Momentary interface freezes while EEVEE rendering causes progress bar malfunction #72339

New Issue

Wilbur Jaywright · 2019-12-10T16:23:14+01:00

Wilbur Jaywright commented

2019-12-10 16:23:14 +01:00

System Information
Operating system: Windows 10, 64 bit
Graphics card: Intel HD Graphics

Blender Version
Broken: 2.80, 2.81

Short description of error
Rendering in EEVEE has been causing momentary complete interface freezes for each frame, which caused the progress bar on the frame render to malfunction and jump very quickly from one value to another, thus giving momentarily true but useless information (note that the progress bar never moved to an incorrect position, it just froze). One thing that assures me this is a bug is minimizing all Blender windows causes the progress bar visible on the minimized icon to work properly (but unfortunately one cannot see what frame it's on).

Exact steps for others to reproduce the error
Open the default blend file.
Render the animation. The interface on 2.81 has frozen for each frame.

**System Information** Operating system: Windows 10, 64 bit Graphics card: Intel HD Graphics **Blender Version** Broken: 2.80, 2.81 **Short description of error** **Rendering in EEVEE has been causing momentary complete interface freezes for each frame**, which caused the progress bar on the frame render to malfunction and jump very quickly from one value to another, thus giving momentarily true but useless information (note that the progress bar never moved to an incorrect position, it just froze). One thing that assures me this is a bug is **minimizing all Blender windows causes the progress bar visible on the minimized icon to work properly** (but unfortunately one cannot see what frame it's on). **Exact steps for others to reproduce the error** Open the default blend file. Render the animation. The interface on 2.81 has frozen for each frame.

Wilbur Jaywright commented

2019-12-10 16:23:14 +01:00

Added subscriber: @zargul

blender-admin commented

2019-12-10 16:23:14 +01:00

#75385 was marked as duplicate of this issue

blender-admin commented

2019-12-10 16:23:14 +01:00

#74504 was marked as duplicate of this issue

blender-admin commented

2019-12-10 16:23:14 +01:00

#73894 was marked as duplicate of this issue

Jeroen Bakker commented

2019-12-11 07:57:05 +01:00

Added subscriber: @Jeroen-Bakker

Jeroen Bakker commented

2019-12-11 07:57:05 +01:00

Changed status from 'Open' to: 'Archived'

Jeroen Bakker closed this issue

2019-12-11 07:57:05 +01:00

Jeroen Bakker self-assigned this 2019-12-11 07:57:05 +01:00

Jeroen Bakker commented

2019-12-11 07:57:05 +01:00

EEVEE renders in the main thread of blender due to OpenGL limitations. Almost all calls to OpenGL needs to be passed to the driver via the main thread. This halts any other work that is handled by the main thread (python scripts ui updates). Same reason that running python scripts halts UI updates.

The progress status is send to the OS, so here it is updated correctly as the rendering is done by OS threads, not by Blender.

EEVEE renders in the main thread of blender due to OpenGL limitations. Almost all calls to OpenGL needs to be passed to the driver via the main thread. This halts any other work that is handled by the main thread (python scripts ui updates). Same reason that running python scripts halts UI updates. The progress status is send to the OS, so here it is updated correctly as the rendering is done by OS threads, not by Blender.

Wilbur Jaywright commented

2019-12-13 03:23:19 +01:00

Right. Thanks!