UI slows down while nodes are being calculated #36393

New Issue

Björn Sonnenschein · 2013-08-05T19:13:44+02:00

2013-08-05 19:13:44 +02:00

Duplicates: #36239

%%%--- Operating System, Graphics card ---
Fedora 18, 64 bit, Nvidia GTX 460, proprietary drivers.

- Blender version with error, and version that worked ---

2.68a, and git show the bug.

- Short description of error ---

While nodes are being calculated, if there is either the backdrop or an UV/Image Editor area is showing a viewer node, the ui gets unresponsive and stutters.
This gets even worse if a scopes panel is visible in the Image Editor.

- Steps for others to reproduce the error (preferably based on attached .blend file) ---

Open the attached blendfile, change the current frame and then drag some nodes around while blender is calculating.

%%%

**Duplicates**: #36239 %%%--- Operating System, Graphics card --- Fedora 18, 64 bit, Nvidia GTX 460, proprietary drivers. - Blender version with error, and version that worked --- 2.68a, and git show the bug. - Short description of error --- While nodes are being calculated, if there is either the backdrop or an UV/Image Editor area is showing a viewer node, the ui gets unresponsive and stutters. This gets even worse if a scopes panel is visible in the Image Editor. - Steps for others to reproduce the error (preferably based on attached .blend file) --- Open the attached blendfile, change the current frame and then drag some nodes around while blender is calculating. %%%

Björn Sonnenschein commented

2013-08-05 19:13:44 +02:00

Changed status to: 'Open'

Björn Sonnenschein commented

2013-08-05 19:18:53 +02:00

%%%Browser crashed while uploading, hopefully the blend gets attached now.%%%

Lukas Tönne commented

2013-08-07 18:44:40 +02:00

%%%I don't get a noticeable slowdown with the basic ui setup in that file, but showing histogram in the image editor clearly shows blocking ui. gprof confirms that a lot of time is spent on scopes_update(), which calculates the scopes data after each image update:
http://www.pasteall.org/44686

Disabling the actual calculation in scopes_update() removes the ui blocking. So, unless we want to move scope updates into an independent non-blocking job, we should probably avoid these very frequent updates. The scopes get tagged dirty all the time during compositor jobs via the ND_COMPO_RESULT notifier -> image_listener callback. The notifiers get set both by a 0.1 second timer as well as on job update, i.e. when the compositor updates its progress.%%%

%%%I don't get a noticeable slowdown with the basic ui setup in that file, but showing histogram in the image editor clearly shows blocking ui. gprof confirms that a lot of time is spent on scopes_update(), which calculates the scopes data after each image update: http://www.pasteall.org/44686 Disabling the actual calculation in scopes_update() removes the ui blocking. So, unless we want to move scope updates into an independent non-blocking job, we should probably avoid these very frequent updates. The scopes get tagged dirty all the time during compositor jobs via the ND_COMPO_RESULT notifier -> image_listener callback. The notifiers get set both by a 0.1 second timer as well as on job update, i.e. when the compositor updates its progress.%%%

Lukas Tönne commented

2013-08-08 08:24:39 +02:00

%%%Same issue with Cycles reported in 36239%%%

Lukas Tönne commented

2013-08-08 14:22:12 +02:00

%%%The problem here is that the scopes updating is slow and it gets repeated frequently during render/compositing. Proper solution would involve making scopes updates an independent threaded job, but that's more of a ToDo than a simple bugfix. Added to our list, for now you'll just have to accept it or close the scopes panel during render/composite, sorry.%%%

Lukas Tönne commented

2013-08-08 14:22:13 +02:00

Changed status from 'Open' to: 'Archived'

Lukas Tönne closed this issue

2013-08-08 14:22:13 +02:00

Björn Sonnenschein commented

2013-08-23 11:39:11 +02:00

%%%Okay, so the problem with the scopes is a known Issue.

For some reason, I also get a slowdown with the basic setup of the file, so without scopes. It seems to me that this is an other Bug, unrelated to the scopes.
Can anyone else reproduce this? Because Lukas can't, I have also tried this on a fresh system and blender build + blender 2.68a release Version to get sure it is not related to some configuration Issues. but still get slowdowns. A video showing the effect is attached now.%%%

%%%Okay, so the problem with the scopes is a known Issue. For some reason, I also get a slowdown with the basic setup of the file, so without scopes. It seems to me that this is an other Bug, unrelated to the scopes. Can anyone else reproduce this? Because Lukas can't, I have also tried this on a fresh system and blender build + blender 2.68a release Version to get sure it is not related to some configuration Issues. but still get slowdowns. A video showing the effect is attached now.%%%

Lukas Tönne commented

2013-08-23 11:58:33 +02:00

%%%Have you tried "Load Factory Settings" (File menu)? It might be some threads setting ... Can you give us more detailed system info (Help->System Info)%%%

Björn Sonnenschein commented

2013-08-25 12:16:40 +02:00

%%%I have attached the system Info and figured out, that the slowdown is caused by the Images Draw Method being set to GLSL. If it is set to 2D Texture or Pixel Draw, the stuttering is greatly reduced.%%%

Sybren A. Stüvel referenced this issue

2023-03-30 15:30:09 +02:00

Blender development todo list -- Editors #55366

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

UI slows down while nodes are being calculated #36393