Viewport: Selecting many objects causes constant CPU usage #46536

New Issue

Jeffrey · 2015-10-19T03:48:14+02:00

Jeffrey commented

2015-10-19 03:48:14 +02:00

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.blend

**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.blend](https://archive.blender.org/developer/F245839/new-depsgraph.blend)

Jeffrey commented

2015-10-19 03:48:14 +02:00

Changed status to: 'Open'

Jeffrey commented

2015-10-19 03:48:14 +02:00

Added subscriber: @italic

Campbell Barton commented

2015-10-19 08:11:55 +02:00

Added subscriber: @ideasman42

Campbell Barton commented

2015-10-19 08:11:55 +02:00

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.

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 commented

2015-10-19 09:31:40 +02:00

In #46536#342386, @ideasman42 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.

> In #46536#342386, @ideasman42 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 commented

2015-10-19 20:01:01 +02:00

Added subscriber: @willi-2

Willi commented

2015-10-19 20:01:01 +02:00

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

Sergey Sharybin commented

2015-10-21 09:02:57 +02:00

Added subscriber: @Sergey

Sergey Sharybin commented

2015-10-21 09:02:57 +02:00

Changed status from 'Open' to: 'Archived'

Sergey Sharybin closed this issue

2015-10-21 09:02:57 +02:00

Sergey Sharybin self-assigned this 2015-10-21 09:02:57 +02:00

Sergey Sharybin commented

2015-10-21 09:02:57 +02:00

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.

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 commented

2015-10-28 16:43:00 +01:00

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.

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

Viewport: Selecting many objects causes constant CPU usage #46536