[BUG] 2.71 use 100% of CPU at sculpt #41193

Closed
opened 2014-07-26 16:54:48 +02:00 by David · 25 comments

At sculpt a random model, for example the cube subdivided 3 times, and sculpt with mouse button hold pressed moving around for 3-5 secs or more start use the 100% of CPU and other programs stop like music player, chrome audio...

*In the 2.70a release version x64 this only use the 15%-30% of cpu at max.

System:

CPU: Intel i7-4770K @ 3.50GHZ
RAM: 16 GB
GPU: Nvidia Geforce 780 GTX
OS: Windows 7 Ultimate, 64-bit, service pack 1
Drivers: Nvidia 337.88
Blender: 2.71 Release x64

At sculpt a random model, for example the cube subdivided 3 times, and sculpt with mouse button hold pressed moving around for 3-5 secs or more start use the 100% of CPU and other programs stop like music player, chrome audio... *In the 2.70a release version x64 this only use the 15%-30% of cpu at max. System: CPU: Intel i7-4770K @ 3.50GHZ RAM: 16 GB GPU: Nvidia Geforce 780 GTX OS: Windows 7 Ultimate, 64-bit, service pack 1 Drivers: Nvidia 337.88 Blender: 2.71 Release x64
Author

Changed status to: 'Open'

Changed status to: 'Open'
Author

Added subscriber: @Hgdavidy

Added subscriber: @Hgdavidy

Added subscriber: @mont29

Added subscriber: @mont29

Added subscriber: @ygtsvtr

Added subscriber: @ygtsvtr

I can confirm that the cpu is using > % 90 . It is like this on multi-res , dynatopo and mesh sculpt.

sculpt_high_cpu.jpg

I can confirm that the cpu is using > % 90 . It is like this on multi-res , dynatopo and mesh sculpt. ![sculpt_high_cpu.jpg](https://archive.blender.org/developer/F99854/sculpt_high_cpu.jpg)

Added subscriber: @kevindietrich

Added subscriber: @kevindietrich

Did a rough test with top here on Linux, and it gives me 141,6% (I believe 100% is 1 core, but ain't really sure)

Did a rough test with `top` here on Linux, and it gives me 141,6% (I believe 100% is 1 core, but ain't really sure)
Author
I read this today http://blenderartists.org/forum/showthread.php?341960-2-71-Sculpting-slow-hangs-and-100-cpu

Added subscriber: @sanctuary

Added subscriber: @sanctuary

I confirm it on my end too on win32 , 2.71 and 2.71 buildbot eat 100% of CPU on any sculpt stroke ! on a sculpt i had started back in 2.70.

And as mentionned in the thread linked by Hgdavidy , i gave a try to today's "Legacy VS 2008" buildbot version, and similarly to 2.70a and before, it only taes +/-50% of CPU at max during sculpt strokes on that same sculpt.

I guess i'll start to stick again to "legacy" buildbot from now.

edit : Maybe related, there were a few people in the modelling support board on blenderartists that started threads about sculpt mode freezing or lagging extremely on their system in 2.71, and while trying back 2.70a it was silk smooth.

I confirm it on my end too on win32 , 2.71 and 2.71 buildbot eat 100% of CPU on any sculpt stroke ! on a sculpt i had started back in 2.70. And as mentionned in the thread linked by Hgdavidy , i gave a try to today's "Legacy VS 2008" buildbot version, and similarly to 2.70a and before, it only taes +/-50% of CPU at max during sculpt strokes on that same sculpt. I guess i'll start to stick again to "legacy" buildbot from now. edit : Maybe related, there were a few people in the modelling support board on blenderartists that started threads about sculpt mode freezing or lagging extremely on their system in 2.71, and while trying back 2.70a it was silk smooth.

Added subscriber: @Ace_Dragon

Added subscriber: @Ace_Dragon

Looking at the thread on BA, you might want to add 'Windows' as one of the project categories.

This being because it's apparent that Linux users have no problem either.

Looking at the thread on BA, you might want to add 'Windows' as one of the project categories. This being because it's apparent that Linux users have no problem either.

Added subscriber: @numarul7

Added subscriber: @numarul7

bugconfirmed.png

Confirmed on Windows 8.1 Pro 64 bit

Core i5 3.2 ghz Nvidia Geforce GTX 650 4 gb

It happens when you draw on the model instantly going 100%.

Blender 3D

version 2.71 (sub 0), branch b'master', commit date b'2014-06-25' b'18:36', hash b'9337574', b'Release'
build date: b'2014-06-25', b'22:33:12'

![bugconfirmed.png](https://archive.blender.org/developer/F99947/bugconfirmed.png) Confirmed on Windows 8.1 Pro 64 bit Core i5 3.2 ghz **Nvidia Geforce GTX 650 4 gb** It happens when you draw on the model instantly going 100%. Blender 3D version 2.71 (sub 0), branch b'master', commit date b'2014-06-25' b'18:36', hash b'9337574', b'Release' build date: b'2014-06-25', b'22:33:12'

Would even say issue seems to be related to MSVC2013, since deprecated builds (using MSVC2008) seems to behave normally…

Would even say issue seems to be related to MSVC2013, since deprecated builds (using MSVC2008) seems to behave normally…

Added subscribers: @MartijnBerger, @Psy-Fi

Added subscribers: @MartijnBerger, @Psy-Fi

This issue was referenced by 115458b53e

This issue was referenced by 115458b53e5e98ee6bc8cd97fcc38cdc51f89df7

Changed status from 'Open' to: 'Resolved'

Changed status from 'Open' to: 'Resolved'

Closed by commit 115458b53e.

Closed by commit 115458b53e.

Changed status from 'Resolved' to: 'Open'

Changed status from 'Resolved' to: 'Open'

Sorry to re-open but it looks like the problem is still there

I just gave a try to today's buildbot , that includes this bugfix and while it's not exactly 100% anymore, it's still a very high CPU usage in comparison to the non-msvc2013 build that had much lower one.

Comparison on the same sculpt (a 500.000 tris dyntopo sculpt), both after enabling dyntopo just doing similar strokes , same brush (crease) , same size, same zoom level, same dyntopo detail, same every setting to be sure the test would be really the same

latest buildbot ( blender-2.71-939503a-win32 ) :
http://i.imgur.com/XL7mQlY.jpg

latest "legacy msvc2008" buildbot ( blender-2.71-a8233d7-win32-vc9 )
http://i.imgur.com/Vfxlft4.jpg
(surprised it used so few CPU on this build and have same performance)

Sorry to re-open but it looks like the problem is still there I just gave a try to today's buildbot , that includes this bugfix and while it's not exactly 100% anymore, it's still a very high CPU usage in comparison to the non-msvc2013 build that had much lower one. Comparison on the same sculpt (a 500.000 tris dyntopo sculpt), both after enabling dyntopo just doing similar strokes , same brush (crease) , same size, same zoom level, same dyntopo detail, same every setting to be sure the test would be really the same latest buildbot ( blender-2.71-939503a-win32 ) : http://i.imgur.com/XL7mQlY.jpg latest "legacy msvc2008" buildbot ( blender-2.71-a8233d7-win32-vc9 ) http://i.imgur.com/Vfxlft4.jpg (surprised it used so few CPU on this build and have same performance)
Member
 could you maybe try setting the environment variable 'OMP_WAIT_POLICY' to  'passive' and see if that has any impact?

scratch that, MS does not support it. All versions of Visual Studio 2010 and greater suffer from this same issue. Microsoft seems to be aware and not really wanting to fix it.

``` could you maybe try setting the environment variable 'OMP_WAIT_POLICY' to 'passive' and see if that has any impact? ``` scratch that, MS does not support it. All versions of Visual Studio 2010 and greater suffer from this same issue. Microsoft seems to be aware and not really wanting to fix it.

Changed status from 'Open' to: 'Archived'

Changed status from 'Open' to: 'Archived'

Moving to TODO now. Fixing this will probably require not using openmp at all here but this is bigger task than a bugfix. As a workaround you can always disable threaded sculpt.

Moving to TODO now. Fixing this will probably require not using openmp at all here but this is bigger task than a bugfix. As a workaround you can always disable threaded sculpt.

Thanks, with threaded sculpt disabled, the CPU usage is much better.

Thanks, with threaded sculpt disabled, the CPU usage is much better.
Sign in to join this conversation.
No Label
Interest
Alembic
Interest
Animation & Rigging
Interest
Asset Browser
Interest
Asset Browser Project Overview
Interest
Audio
Interest
Automated Testing
Interest
Blender Asset Bundle
Interest
BlendFile
Interest
Collada
Interest
Compatibility
Interest
Compositing
Interest
Core
Interest
Cycles
Interest
Dependency Graph
Interest
Development Management
Interest
EEVEE
Interest
EEVEE & Viewport
Interest
Freestyle
Interest
Geometry Nodes
Interest
Grease Pencil
Interest
ID Management
Interest
Images & Movies
Interest
Import Export
Interest
Line Art
Interest
Masking
Interest
Metal
Interest
Modeling
Interest
Modifiers
Interest
Motion Tracking
Interest
Nodes & Physics
Interest
OpenGL
Interest
Overlay
Interest
Overrides
Interest
Performance
Interest
Physics
Interest
Pipeline, Assets & IO
Interest
Platforms, Builds & Tests
Interest
Python API
Interest
Render & Cycles
Interest
Render Pipeline
Interest
Sculpt, Paint & Texture
Interest
Text Editor
Interest
Translations
Interest
Triaging
Interest
Undo
Interest
USD
Interest
User Interface
Interest
UV Editing
Interest
VFX & Video
Interest
Video Sequencer
Interest
Virtual Reality
Interest
Vulkan
Interest
Wayland
Interest
Workbench
Interest: X11
Legacy
Blender 2.8 Project
Legacy
Milestone 1: Basic, Local Asset Browser
Legacy
OpenGL Error
Meta
Good First Issue
Meta
Papercut
Meta
Retrospective
Meta
Security
Module
Animation & Rigging
Module
Core
Module
Development Management
Module
EEVEE & Viewport
Module
Grease Pencil
Module
Modeling
Module
Nodes & Physics
Module
Pipeline, Assets & IO
Module
Platforms, Builds & Tests
Module
Python API
Module
Render & Cycles
Module
Sculpt, Paint & Texture
Module
Triaging
Module
User Interface
Module
VFX & Video
Platform
FreeBSD
Platform
Linux
Platform
macOS
Platform
Windows
Priority
High
Priority
Low
Priority
Normal
Priority
Unbreak Now!
Status
Archived
Status
Confirmed
Status
Duplicate
Status
Needs Info from Developers
Status
Needs Information from User
Status
Needs Triage
Status
Resolved
Type
Bug
Type
Design
Type
Known Issue
Type
Patch
Type
Report
Type
To Do
No Milestone
No project
No Assignees
11 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: blender/blender#41193
No description provided.