Blender Does Not Account for Suspend #43597

New Issue

Zauber Paracelsus · 2015-02-08T17:28:32+01:00

Zauber Paracelsus commented

2015-02-08 17:28:32 +01:00

System Information
64bit Manjaro Linux, kernel 3.14.29
CPU: AMD Phenom II 970 Deneb quad-core
GPU: nVidia GTX 650 Ti, driver 343.36

Blender Version
Broken: Buildbot Build 2.73 4cbf2ebd
Worked: Not sure this ever worked

Short description of error
Each night when I go to bed, I put my computer into suspend mode, rather than just leaving it on or shutting down. Most applications I leave running during the night don't have any problems. Blender, however, does. Two main problems I have observed:

Textures on models will often be garbled.
Rendering in cycles with CUDA will fail until you close blender and reopen it.

Exact steps for others to reproduce the error

Start blender from the command line, and open or create a scene with textured surfaces, set Cycles to GPU mode. Go to the Render->Performance tab, and make sure that Persistent Images is turned on.
Render the scene. It should render normally.
Exit rendered view, go back to 3D view.
Put your computer into suspend for at least 30 seconds.
Exit suspend mode. Textures on the model will be garbled.
Attempt to render. The render will fail, and if you click or touch anything you will get error messages about illegal instructions on the command line.
Reload the file. The model textures will be corrected.
Attempt to render. It will still fail to render, with the same illegal instruction errors.
Close and reopen blender, then go to the Render->Performance tab and turn the Persistent Images option off.
Repeat steps 1-8 with Persistent Images disabled. The texture corruption still occurs, but the CUDA errors do not.

Fixing the issue should be simple (in theory). It could be done by detecting when the computer suspends or hibernates (most OS's should provide an interface to detect this, but I could be wrong) and then clear/reload the data stored on the GPU.

Error output I got: CUDA_Errors.txt

**System Information** 64bit Manjaro Linux, kernel 3.14.29 CPU: AMD Phenom II 970 Deneb quad-core GPU: nVidia GTX 650 Ti, driver 343.36 **Blender Version** Broken: Buildbot Build 2.73 4cbf2ebd Worked: Not sure this ever worked **Short description of error** Each night when I go to bed, I put my computer into suspend mode, rather than just leaving it on or shutting down. Most applications I leave running during the night don't have any problems. Blender, however, does. Two main problems I have observed: - Textures on models will often be garbled. - Rendering in cycles with CUDA will fail until you close blender and reopen it. **Exact steps for others to reproduce the error** 1) Start blender from the command line, and open or create a scene with textured surfaces, set Cycles to GPU mode. Go to the Render->Performance tab, and make sure that Persistent Images is turned on. 2) Render the scene. It should render normally. 3) Exit rendered view, go back to 3D view. 4) Put your computer into suspend for at least 30 seconds. 5) Exit suspend mode. Textures on the model will be garbled. 6) Attempt to render. The render will fail, and if you click or touch anything you will get error messages about illegal instructions on the command line. 7) Reload the file. The model textures will be corrected. 8) Attempt to render. It will still fail to render, with the same illegal instruction errors. 9) Close and reopen blender, then go to the Render->Performance tab and turn the Persistent Images option off. 10) Repeat steps 1-8 with Persistent Images disabled. The texture corruption still occurs, but the CUDA errors do not. Fixing the issue should be simple (in theory). It could be done by detecting when the computer suspends or hibernates (most OS's should provide an interface to detect this, but I could be wrong) and then clear/reload the data stored on the GPU. Error output I got: [CUDA_Errors.txt](https://archive.blender.org/developer/F141930/CUDA_Errors.txt)

Zauber Paracelsus commented

2015-02-08 17:28:32 +01:00

Changed status to: 'Open'

Zauber Paracelsus commented

2015-02-08 17:28:32 +01:00

Added subscriber: @ZauberParacelsus

Bastien Montagne commented

2015-02-08 17:46:55 +01:00

Added subscribers: @Sergey, @Psy-Fi, @mont29

Bastien Montagne commented

2015-02-08 17:46:55 +01:00

Not quite sure we can do anything here… Afaik, suspending an OpenGL (or DirectX, for what matters) application is always problematic, it uses specific low-level access to the GPU driver, unlike regular applications which only use OS APIs. Antony or Sergey should know better here, though.

Zauber Paracelsus commented

2015-02-08 17:48:20 +01:00

@mont29 - Yeah, that's why I said it would be simple "in theory". And because I know that nothing is truly simple with programming, lol.

Sergey Sharybin commented

2015-02-09 12:41:11 +01:00

Changed status from 'Open' to: 'Archived'

Sergey Sharybin closed this issue

2015-02-09 12:41:11 +01:00

Sergey Sharybin self-assigned this 2015-02-09 12:41:11 +01:00

Sergey Sharybin commented

2015-02-09 12:41:11 +01:00

You can think of hibernation as something totally transparent for application -- it just should not notice anything happened. You can't fix it from userspace (aka blender in this case). Some workarounds are probably possible, but it'll be really nasty code which would still fail in loads of cases (for example on my laptop probability of ogl stuck at 100% CPU usage after hibernation is quite high, this you can't fix from blender without restarting it).

So thanks for the report, but we can't really do much about this. Ideally nvidia should look into their driver, but from quick google seems they're not really interested in solving this =/

You can think of hibernation as something totally transparent for application -- it just should not notice anything happened. You can't fix it from userspace (aka blender in this case). Some workarounds are probably possible, but it'll be really nasty code which would still fail in loads of cases (for example on my laptop probability of ogl stuck at 100% CPU usage after hibernation is quite high, this you can't fix from blender without restarting it). So thanks for the report, but we can't really do much about this. Ideally nvidia should look into their driver, but from quick google seems they're not really interested in solving this =/

Antonis Ryakiotakis commented

2015-02-09 12:59:43 +01:00

There is such a thing as a robust context in newer OpenGL, check https://www.opengl.org/registry/specs/ARB/robustness.txt. We could try using it but I'm not certain it will fix resets in CUDA contexts...Any CUDA guru here who might know? I'd suggest to use command-line only rendering for such tasks for now.

Sergey Sharybin commented

2015-02-09 13:22:54 +01:00

@Psy-Fi, i'm not sure why exactly the robust contexts will help? From the problem description it just seems driver is flacky enough to not ensure row refresh signals are keeping to happen on video card's SDRAM, which eventually leads to textures corruption. At least that's what likely happening based on the timing and symptoms. Not totally clear why other contents of VRAM are fine tho.

In any case, opengl+hibernation issue is not something blender-specific, it's kernel+driver specific. My main desktop seems to survive it all just fine i.e.

CUDA+hibernation is major problems, being discussed in loads of places. Driver is just to be fixed..

@Psy-Fi, i'm not sure why exactly the robust contexts will help? From the problem description it just seems driver is flacky enough to not ensure row refresh signals are keeping to happen on video card's SDRAM, which eventually leads to textures corruption. At least that's what likely happening based on the timing and symptoms. Not totally clear why other contents of VRAM are fine tho. In any case, opengl+hibernation issue is not something blender-specific, it's kernel+driver specific. My main desktop seems to survive it all just fine i.e. CUDA+hibernation is major problems, being discussed in loads of places. Driver is just to be fixed..

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

Blender Does Not Account for Suspend #43597