Blender 3.0b becomes laggy after being open for some time #93114

New Issue

Gabriel · 2021-11-16T05:19:05+01:00

Gabriel commented

2021-11-16 05:19:05 +01:00

System Information
Operating system: Windows 10 Home
Graphics card: Intel Iris XE

Blender Version
Broken: 3.0, bd734cc441
Worked: (newest version of Blender that worked as expected)

So I just noticed that Blender was behaving a bit choppy. This is to be expected if you're in Rendered shading mode, but I tried to go to Solid view and it was still lagging. I finally got fed up with this and restarted the application, and then that fixed the lag, even opening the same blend file did not cause it again.

That made it a LOT smoother in comparison. After a few hours, it happened again, first to the 3D viewport and eventually the node editor as well, which I was struggling with, and restarting fixed that again.

So I'm not sure what is causing it- whether it's dependent on what you do, the undo history, console, or just time since opening. I don't know if it's been fixed in a newer build after 11/11, but if that's been tested, I still want to know, I appreciate anything in advance.

Exact steps for others to reproduce the error
Leave blender open for a few hours or do something in the program. Not sure if it's to do with texture baking specifically, but that is something I was doing.

**System Information** Operating system: Windows 10 Home Graphics card: Intel Iris XE **Blender Version** Broken: 3.0, bd734cc4419a Worked: (newest version of Blender that worked as expected) So I just noticed that Blender was behaving a bit choppy. This is to be expected if you're in Rendered shading mode, but I tried to go to Solid view and it was still lagging. I finally got fed up with this and restarted the application, and then that fixed the lag, even opening the same blend file did not cause it again. That made it a LOT smoother in comparison. After a few hours, it happened again, first to the 3D viewport and eventually the node editor as well, which I was struggling with, and restarting fixed that again. So I'm not sure what is causing it- whether it's dependent on what you do, the undo history, console, or just time since opening. I don't know if it's been fixed in a newer build after 11/11, but if that's been tested, I still want to know, I appreciate anything in advance. **Exact steps for others to reproduce the error** Leave blender open for a few hours or do something in the program. Not sure if it's to do with texture baking specifically, but that is something I was doing.

Gabriel commented

2021-11-16 05:19:05 +01:00

Added subscriber: @CuriousHobbyist

Stay_Here commented

2021-11-16 05:41:48 +01:00

Added subscriber: @Stay_Here

Stay_Here commented

2021-11-16 05:41:48 +01:00

I have probably the same problem with the 3.0 Beta. When the lag happens, the delayed update in the solid view can be frustrated when navigating in the 3D viewport.

The lag remains, even after I clicked "File" -> "New" -> "General". The default cube can be hard to navigate and view in the viewport.

The only fix is to restart the program.

I have probably the same problem with the 3.0 Beta. When the lag happens, the delayed update in the solid view can be frustrated when navigating in the 3D viewport. The lag remains, even after I clicked "File" -> "New" -> "General". The default cube can be hard to navigate and view in the viewport. The only fix is to restart the program.

Gabriel commented

2021-11-16 06:31:10 +01:00

+GoBlender Is it a newer build though? Mine was 11/11/21.

Stay_Here commented

2021-11-17 00:03:22 +01:00

My build was from 10/30/21, not as new as yours.

The most likely scenario in my case is when two or more Blender(s) are launched. For example, open Blender.exe twice, then load two different characters in the two Blender windows. Let's say, character A and character B are loaded in the Blender window A and window B, respectively. After that, I spend some time on sculpting character A, and use the character B as a reference character. In this setup, Blender window B is seldom touched or manipulated, since it is just for reference.

After about 10 mins to 2 hours on sculpting character A on the window A and open YouTube to listen some music, I jump to the Blender window B to navigate and change the view to the reference character B. At this moment, the lag in the solid viewport in the window B can be quite likely to happen. However, at the same moment, navigating in the window A is still smooth and unaffected.

To fix this, I shutdown the Blender B, and reopen Blend.exe and reload the character B. Everything becomes normal and smooth.

During the lag, I observed that the usage on my CPU and GPU are below 10%, and the usage on my memory are below 20 GB (I have 64 GB memory). I forget how much the usage on the data transmission on my SSD is, but most likely I guess that the transmission rate is unchanged and does not suddenly increase during the lag.

My build was from 10/30/21, not as new as yours. The most likely scenario in my case is when two or more Blender(s) are launched. For example, open Blender.exe twice, then load two different characters in the two Blender windows. Let's say, character A and character B are loaded in the Blender window A and window B, respectively. After that, I spend some time on sculpting character A, and use the character B as a reference character. In this setup, Blender window B is seldom touched or manipulated, since it is just for reference. After about 10 mins to 2 hours on sculpting character A on the window A and open YouTube to listen some music, I jump to the Blender window B to navigate and change the view to the reference character B. At this moment, the lag in the solid viewport in the window B can be quite likely to happen. However, at the same moment, navigating in the window A is still smooth and unaffected. To fix this, I shutdown the Blender B, and reopen Blend.exe and reload the character B. Everything becomes normal and smooth. During the lag, I observed that the usage on my CPU and GPU are below 10%, and the usage on my memory are below 20 GB (I have 64 GB memory). I forget how much the usage on the data transmission on my SSD is, but most likely I guess that the transmission rate is unchanged and does not suddenly increase during the lag.

Gabriel commented

2021-11-17 00:42:53 +01:00

10/30 huh? I was not expecting that at all because we do tend to wonder if newer builds fix issues. What I was wondering is if it's been fixed after 11/11. Also interesting that it only happens to one instance.

10/30 huh? I was not expecting that at all because we do tend to wonder if **newer** builds fix issues. What I was wondering is if it's been fixed after 11/11. Also interesting that it only happens to one instance.

Stay_Here commented

2021-11-17 03:02:32 +01:00

Since 10/30/21, it has already happened to me for more than 3 times.

I can tell you that it's not going to be fixed until developers are able to reproduce the problem. So far, it is very hard for developers to reproduce the problem, which only happens under certain and unknown condition(s).

So I don't expect this problem is going to be fixed anytime soon, and I expect that this thread is going to be closed soon, unless they can reproduce the problem.

Since 10/30/21, it has already happened to me for more than 3 times. I can tell you that it's not going to be fixed until developers are able to reproduce the problem. So far, it is very hard for developers to reproduce the problem, which only happens under certain and unknown condition(s). So I don't expect this problem is going to be fixed anytime soon, and I expect that this thread is going to be closed soon, unless they can reproduce the problem.

Stay_Here commented

2021-11-17 07:11:32 +01:00

bug1.mp4
Today, I have encountered the same problem again as shown on the short video I uploaded. Due to the copyright and NDA issue from the client, the original blender scene can not be shown in this video, which only shows that the lag of navigation in the solid viewport remains even after I clicked "File" -> "New" -> "General". From the video, you can also see that the lag disappears when I click the gizmo axis to navigate instead.

During the lag, the video shows that the usage of CPU and GPU and SSD are very low, but the usage on the memory can be misleading. The Task Manager shows that Blender only use 2223 MB on my memory, but the total usage of the memory of the whole system is about 20 GB. There are two reasons:

1, After the lag occurred, I then opened another Blender.exe to check if my client scene is saved properly or not, then closed this Blender.exe after my check. This shutdown caused the original Blender.exe (the laggy one) to "drop" the memory usage from 12.8 GB to 2223 MB.

2, But it is not really a "drop", the total usage of the memory of the whole system is still about 20 GB. The Task Manager may misrepresent the actual memory usage of the Blender. The Resource Monitor shows that 12.2 GB is used for the memory compression instead, and 31.4 GB is committed to Blender.

The following screenshot show how much usage on the memory really is on the Task Manager, when the default cube is loaded and is laggy to navigate. The original Blender.exe used 12.8 GB and the whole system used 26 GB.

[bug1.mp4](https://archive.blender.org/developer/F11817958/bug1.mp4) Today, I have encountered the same problem again as shown on the short video I uploaded. Due to the copyright and NDA issue from the client, the original blender scene can not be shown in this video, which only shows that the lag of navigation in the solid viewport remains even after I clicked "File" -> "New" -> "General". From the video, you can also see that the lag disappears when I click the gizmo axis to navigate instead. During the lag, the video shows that the usage of CPU and GPU and SSD are very low, but the usage on the memory can be misleading. The Task Manager shows that Blender only use 2223 MB on my memory, but the total usage of the memory of the whole system is about 20 GB. There are two reasons: 1, After the lag occurred, I then opened another Blender.exe to check if my client scene is saved properly or not, then closed this Blender.exe after my check. This shutdown caused the original Blender.exe (the laggy one) to "drop" the memory usage from 12.8 GB to 2223 MB. 2, But it is not really a "drop", the total usage of the memory of the whole system is still about 20 GB. The Task Manager may misrepresent the actual memory usage of the Blender. The Resource Monitor shows that 12.2 GB is used for the memory compression instead, and 31.4 GB is committed to Blender. ![resource4.jpg](https://archive.blender.org/developer/F11818086/resource4.jpg) The following screenshot show how much usage on the memory really is on the Task Manager, when the default cube is loaded and is laggy to navigate. The original Blender.exe used 12.8 GB and the whole system used 26 GB. ![resource1.jpg](https://archive.blender.org/developer/F11818010/resource1.jpg) ![resource2.jpg](https://archive.blender.org/developer/F11818012/resource2.jpg)

Stay_Here commented

2021-11-17 07:40:26 +01:00

This is what happens after all Blender apps were closed. Based on this, my estimation is that the default cube scene ate more than 12 GB memory.

This is what happens after all Blender apps were closed. Based on this, my estimation is that the default cube scene ate more than 12 GB memory. ![resource6.jpg](https://archive.blender.org/developer/F11818115/resource6.jpg) ![resource7.jpg](https://archive.blender.org/developer/F11818117/resource7.jpg)

Germano Cavalcante commented

2021-11-17 12:44:43 +01:00

Added subscriber: @mano-wii

Germano Cavalcante commented

2021-11-17 12:44:43 +01:00

This reminds me of the bug reported in #93039 (Memory leak while rotating the viewport (default cube)).
In fact it deserves attention.
I've been navigating with the default cube for a while but I don't see any significant change in memory usage.

Does the problem occurs with the factory settings (File → Defaults → Load Factory Settings)?
Is it important to move the cube, sculpt or something similar?

This reminds me of the bug reported in #93039 (Memory leak while rotating the viewport (default cube)). In fact it deserves attention. I've been navigating with the default cube for a while but I don't see any significant change in memory usage. Does the problem occurs with the factory settings (File → Defaults → Load Factory Settings)? Is it important to move the cube, sculpt or something similar?

Germano Cavalcante commented

2021-11-17 13:05:36 +01:00

Both report show that Intel Iris XE was used.
@Stay_Here, can you check the GPU in your system?
You can see this information in the system_info.txt generated in Help -> Save System Info

Both report show that `Intel Iris XE` was used. @Stay_Here, can you check the GPU in your system? You can see this information in the `system_info.txt` generated in `Help -> Save System Info`

Raimund Klink commented

2021-11-17 13:07:35 +01:00

Added subscriber: @Raimund58

Raimund Klink commented

2021-11-17 13:07:35 +01:00

@CuriousHobbyist Could you please go to Help -> Save System Info and upload it here?

@CuriousHobbyist Could you please go to `Help` -> `Save System Info` and upload it here?

Gabriel commented

2021-11-17 19:37:48 +01:00

Added subscriber: @Germano

Gabriel commented

2021-11-17 19:37:48 +01:00

@Raimund Klink) Ok system-info.txt

@mano-wii What build is it though? Mine was 11/11 and GoBlender was using 10/30. The lag seems to happen hours after opening a file and as GoBlender said, to only one instance at a time. Are you using a newer build that fixed it or something?

@Raimund Klink) Ok [system-info.txt](https://archive.blender.org/developer/F11820455/system-info.txt) @mano-wii What build is it though? Mine was 11/11 and GoBlender was using 10/30. The lag seems to happen hours after opening a file and as GoBlender said, to only one instance at a time. Are you using a newer build that fixed it or something?

Stay_Here commented

2021-11-18 04:30:25 +01:00

The system-info.txt

I've been navigating with the default cube for a while but I don't see any significant change in memory usage.

@Germano Cavalcante (mano-wii), the "default cube scene" is an illusion, which disguises the underlying and original scene. I use this "default cube scene" as a name to label the true scene,
After the lag occurred in the original scene, I click "File" -> "New" -> "General", which creates this "default cube scene", but the usage of the system memory does not drop down, and still stays the same even if the cube scene is much simpler than the original scene. This means that the original scene might still be there.

According to my system info, my Blender does not use my Intel Iris integrated graphic chip to render. The relatively higher usage of my Intel Iris GPU you watched in the video above was due to the use of OBS studio to record the video. Thank you!

[The system-info.txt](https://archive.blender.org/developer/F11821986/The_system-info.txt) > I've been navigating with the default cube for a while but I don't see any significant change in memory usage. @Germano Cavalcante (mano-wii), the "default cube scene" is an illusion, which disguises the underlying and original scene. I use this "default cube scene" as a name to label the true scene, After the lag occurred in the original scene, I click "File" -> "New" -> "General", which creates this "default cube scene", but the usage of the system memory does not drop down, and still stays the same even if the cube scene is much simpler than the original scene. This means that the original scene might still be there. According to my system info, my Blender does not use my Intel Iris integrated graphic chip to render. The relatively higher usage of my Intel Iris GPU you watched in the video above was due to the use of OBS studio to record the video. Thank you!

Germano Cavalcante commented

2021-11-18 13:42:49 +01:00

Closed as duplicate of #86778

Germano Cavalcante closed this issue

2021-11-18 13:42:49 +01:00

Sign in to join this conversation.

No Label

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

Blender 3.0b becomes laggy after being open for some time #93114