Page MenuHome
Create Task
Maniphest T46536

Viewport: Selecting many objects causes constant CPU usage
Closed, ArchivedPublic
Actions

Description

System Information
Centos 7 x64
GTX 970 (main) + 560 Ti (secondary)
driver version 355.11

Blender Version
Broken: 2.76 + master bfdb420
Worked: 2.75a official release

Short description of error
Having a massive number of objects selected in the viewport causes blender process to consume an entire core, despite no interaction with the software. This happens with both new and old depsgraphs (use new graph for this report).

Exact steps for others to reproduce the error
Open provided blend with new depsgraph. Deselect all objects and look at your CPU usage. It should be zero. Now select all objects. I've seen one entire core used, hopping among my 6 cores constantly. I've only gotten a readout from my terminal once, and that read "Too many objects in select buffer" - I haven't been able to recreate that message.

I open the same file in 2.75a official release and I don't get the high CPU usage, although I get the same viewport sluggishness inherent to having hundreds or thousands of objects selected (2.76 is much slower, but that might be a different report).

new-depsgraph.blend279 KBDownload

Related Objects

Event Timeline

Jeffrey Hoover (italic_) created this task.Oct 19 2015, 3:48 AM
Jeffrey Hoover (italic_) raised the priority of this task from to 90.
Jeffrey Hoover (italic_) updated the task description. (Show Details)
Jeffrey Hoover (italic_) added a project: BF Blender.
Jeffrey Hoover (italic_) edited a custom field.
Jeffrey Hoover (italic_) added a subscriber: Jeffrey Hoover (italic_).
Campbell Barton (campbellbarton) added a subscriber: Campbell Barton (campbellbarton).EditedOct 19 2015, 8:11 AM

Can't redo this on ArchLinux with 2.76.

Started with: blender --factory-startup --enable-new-depsgraph

Things to try:

  • factory settings - --factory-startup.
  • disable audio in system prefs.
  • you could try profiling this with http://sysprof.com, which can give some useful info even on non-debug builds.
Jeffrey Hoover (italic_) added a comment.Oct 19 2015, 9:31 AM
In T46536#342386, @Campbell Barton (campbellbarton) wrote:

Can't redo this on ArchLinux with 2.76.

Started with: blender --factory-startup --enable-new-depsgraph

I guess it's time to redo my prefs again. I got the same result you did and couldn't bring it back, even when manually copying all my old prefs over to the system prefs. But I load my prefs and I have terrible performance. Maybe it's one of my addons. I'll have to explore that at another time.

Willi (willi) added a subscriber: Willi (willi).Oct 19 2015, 8:01 PM

FYI, can't repro on Win7/64, GTX 750 Ti, Blender 2.76 official

Sergey Sharybin (sergey) changed the task status from Unknown Status to Unknown Status.Oct 21 2015, 9:02 AM
Sergey Sharybin (sergey) claimed this task.
Sergey Sharybin (sergey) added a subscriber: Sergey Sharybin (sergey).

That's possibly some addon which operates on the selection. So please try deducting which exact addon is causing this and submit bug to that addon.

Archiving the report since it's most likely an addon issue.

Jeffrey Hoover (italic_) added a comment.Oct 28 2015, 4:43 PM

Just to follow up, this seems to be caused by the animation nodes package. I'll bring it up with Jackes when I get the chance.