Random Spikes in memory and CPU usage and freezing (4.0.0) #114864

New Issue

Jordan-Cruz · 2023-11-14T19:51:42+01:00

Jordan-Cruz commented

2023-11-14 19:51:42 +01:00

System Information
Operating system: EndeavourOS Linux Kernel 6.5.9 zen
Graphics card: Nvidia GeforceRTX 3060 Lite Hash 12GB, Vram 32GB system RAM

Blender Version
Broken: 4.0.0 (brand new release as of Tues Nov 14, 2023)
Worked: All previous versions

Short description of error
when in wireframe and edit mode (possibly not even just wireframe), eventually the application will lock up after a while at random. I've noticed it to commonly occur when deselecting all verticies/planes/edges. when it occurs CPU jumps from ~0.20 to 99% usage or RAM goes from 1.6gb to 9gb.
Exact steps for others to reproduce the error
Its difficult to show, since it seems almost random. attached is a file where I discovered the issue. theres nothing special about the file as far as I'm aware that could cause the issue. but if you select the floor, tab into edit mode and select all and deselect (double hit A) enough times or after an amount of action is done, it will eventually lock up. flooding memory and CPU. after a while It releases and calms down but I don't see any reason for this specific file to cause that.

**System Information** Operating system: EndeavourOS Linux Kernel 6.5.9 zen Graphics card: Nvidia GeforceRTX 3060 Lite Hash 12GB, Vram 32GB system RAM **Blender Version** Broken: 4.0.0 (brand new release as of Tues Nov 14, 2023) Worked: All previous versions **Short description of error** when in wireframe and edit mode (possibly not even just wireframe), eventually the application will lock up after a while at random. I've noticed it to commonly occur when deselecting all verticies/planes/edges. when it occurs CPU jumps from ~0.20 to 99% usage or RAM goes from 1.6gb to 9gb. **Exact steps for others to reproduce the error** Its difficult to show, since it seems almost random. attached is a file where I discovered the issue. theres nothing special about the file as far as I'm aware that could cause the issue. but if you select the floor, tab into edit mode and select all and deselect (double hit A) enough times or after an amount of action is done, it will eventually lock up. flooding memory and CPU. after a while It releases and calms down but I don't see any reason for this specific file to cause that.

Magicbunker example of error.blend

1.1 MiB

Jordan-Cruz added the

labels 2023-11-14 19:51:43 +01:00

Pratik Borhade commented

2023-11-23 07:47:46 +01:00

Hi, unable to confirm this locally. Does this happen when undo steps are set to 0: Edit > Preferences > System > Memory and Limits > Undo Steps
Also worth to try with factory settings: File > Defaults > Load Factory Settings

Hi, unable to confirm this locally. Does this happen when undo steps are set to 0: `Edit > Preferences > System > Memory and Limits > Undo Steps` Also worth to try with factory settings: `File > Defaults > Load Factory Settings`

Pratik Borhade added

Status

Needs Information from User

and removed

Status

Needs Triage

labels 2023-11-23 07:47:53 +01:00

Peter-Olschinsky commented

2023-11-23 20:02:56 +01:00

Exactly same issue!!!!

CPU jumps to 99 % when in edit mode.

windows 10
AMD Ryzen Threadripper 3970X 32-Core Processor 3.69 GHz
Nvidia Geforce 3090 RTX
128 RAM

Exactly same issue!!!! CPU jumps to 99 % when in edit mode. windows 10 AMD Ryzen Threadripper 3970X 32-Core Processor 3.69 GHz Nvidia Geforce 3090 RTX 128 RAM

Mateusz-42 commented

2023-12-03 19:24:55 +01:00

I am experiencing similar issue.

At first I thought it was random but after some testing I was able to confirm that (at least in my case), it's the undo action that is causing excessive CPU usage.

Here is a way that I've found, which allows to reproduce this "bug":

• Spawn a default cube and select it.
• Add Subdivision Surface modifier and set its levels to 3.
• Apply the modifier — we should end up with an object that has 384 faces.
• Add new Subdivision Surface modifier and once again, set its levels to 3 but this time do not apply it.
• Go into edit mode.
• Implement some random changes to build up few undo steps.
• Select any vert, move it to a different location and apply the change.
• Use undo/redo shortcuts a couple of times (ctrl+z > ctrl+shift+z > ctrl+z > ctrl+shift+z and so on).

That's it...

I am pretty sure that this is not a hardware related issue, because:

This is a new problem that didn't exist before 4.0. If it did, I would have easily noticed it due to the nature of my workflow.
My brother and a friend, who both own different rigs, were able to confirm the existance of the exact same problem.
I think it's important to add, that unlike OP have stated, we do not experience any freezing and/or extra problems with the memory.

I am experiencing similar issue. At first I thought it was random but after some testing I was able to confirm that (at least in my case), it's the undo action that is causing excessive CPU usage. Here is a way that I've found, which allows to reproduce this "bug": • Spawn a default cube and select it. • Add Subdivision Surface modifier and set its levels to 3. • Apply the modifier — we should end up with an object that has 384 faces. • Add new Subdivision Surface modifier and once again, set its levels to 3 but this time do not apply it. • Go into edit mode. • Implement some random changes to build up few undo steps. • Select any vert, move it to a different location and apply the change. • Use undo/redo shortcuts a couple of times (ctrl+z > ctrl+shift+z > ctrl+z > ctrl+shift+z and so on). That's it... I am pretty sure that this is not a hardware related issue, because: 1. This is a new problem that didn't exist before 4.0. If it did, I would have easily noticed it due to the nature of my workflow. 2. My brother and a friend, who both own different rigs, were able to confirm the existance of the exact same problem. I think it's important to add, that unlike OP have stated, we do not experience any freezing and/or extra problems with the memory.

Micah-Ganske commented

2023-12-04 03:52:20 +01:00

Having the same issue where undo operations cause the CPU to spike to 100% and causes everything to freeze for up to 5 seconds. For me, this is happening most noticeably in Sculpt mode and it happens whether I have a Mult-res modifier active or not. It also happens with relatively low-poly meshes.

I tried setting the undo steps to "0" and surprisingly, the same thing happens even though no undo is actually performed. I have a Ryzen 7950X, 64GB RAM, and RTX 3090.

This does not occur in 3.6 with the same settings.

Having the same issue where undo operations cause the CPU to spike to 100% and causes everything to freeze for up to 5 seconds. For me, this is happening most noticeably in Sculpt mode and it happens whether I have a Mult-res modifier active or not. It also happens with relatively low-poly meshes. I tried setting the undo steps to "0" and surprisingly, the same thing happens even though no undo is actually performed. I have a Ryzen 7950X, 64GB RAM, and RTX 3090. This does not occur in 3.6 with the same settings.

Micah-Ganske commented

2023-12-04 04:05:01 +01:00

Well, the error is not present when starting blender with factory settings so it might be a bad addon. Time to searching for a culprit. Will report back if I find something.

Micah-Ganske commented

2023-12-04 06:27:23 +01:00

I found the culprit on my system and it was... the Asset Library!

My asset library is pretty large at 276GB but why should that be causing the CPU to shoot up to 100% when doing an undo?
I thought I was crazy, but adding my asset libraries to a factory fresh install with clean prefs will cause the same undo hitching. I should also add that all the drives on my system are PCIE Gen4 nvme so speed isn't an issue.

Can anyone else with this issue try loading a version of your prefs without the libraries and see if it fixes it for you?

I found the culprit on my system and it was... the Asset Library! My asset library is pretty large at 276GB but why should that be causing the CPU to shoot up to 100% when doing an undo? I thought I was crazy, but adding my asset libraries to a factory fresh install with clean prefs will cause the same undo hitching. I should also add that all the drives on my system are PCIE Gen4 nvme so speed isn't an issue. Can anyone else with this issue try loading a version of your prefs without the libraries and see if it fixes it for you?

Pratik Borhade commented

2023-12-04 06:30:58 +01:00

@Micah-Ganske : #115372

👍 1

Pratik Borhade referenced this issue

2023-12-04 08:51:52 +01:00

Assett library populated with assetts affects mesh editing function #115643

Pratik Borhade referenced this issue

2023-12-04 11:40:27 +01:00

Blender 4.0.1 uses 100% CPU just by switching to Edit mode (or when moving vertex/faces) #115724

Squigglyman commented

2023-12-06 01:36:40 +01:00

This problem persists in "blender-4.0.2-stable+v40.9be62e85b727-windows.amd64-release" just tested. Edit mode is affected by having a large asset library.