Page MenuHome
Create Task
Maniphest T37480

Cycles on the GPU crashes if switching the 3D view display mode to Rendered while in camera view
Closed, ArchivedPublic
Actions

Description

System Information
Windows 7 Professional 64-bit SP1
Intel Core-i7 4700MQ @2.40 Ghz - 16 GB RAM
NVidia GeForce GT 750M 2GB DDR3 - driver v331.65 (latest available from NVIDIA).

Blender Version
Broken: Blender 2.69 r60995 - Blender 2.68a r58537
Worked: ???

Short description of error
With complex scenes, cycles on the GPU crashes when switching the 3d view to rendered
mode incamera view, while rendering with F12 works fine (both with progressive refine on and off).

When the crash occurs, Windows displays an error dialog saying:
"The NVIDIA OpenGL driver detected a problem with the display
driver and is unable to continue. The application must close.
Error code: 3"

Then, a bubble pops up from the traybar saying (Translated from Italian):
"The video driver has stopped responding and has been reset.
The NVIDIA video driver Windows Kernel Mode Driver, Versione 331.65 has stopped responding
and has been correctly reset."

Exact steps for others to reproduce the error
Is seems this problem only happens with certain complex scenes.

One example is Mike Pan's BMW1M:

  1. Download http://dl.dropbox.com/u/1742071/1m/BMW1M-MikePan.blend
  2. Switch the 3D view to Rendered mode.
  3. After rendering a couple of samples, Blender crashes.

Note that switching to Rendered mode doesn't crash if I do one of the following actions:

  • Hide the car shell.
  • Zoom the 3D view out, while still in camera view.
  • Set a render border (shift-B) around the camera view.
  • Set the camera to orthographic mode.

If I then go back to camera view in perspective mode, the crash happens again.

As I said above, rendering with F12 works without problems, and the renderd mode of the 3d view doesn't crash when rendering on the CPU.

Alessandro

Event Timeline

Alessandro Sala (xela) created this task.Nov 15 2013, 10:01 PM
Alessandro Sala (xela) raised the priority of this task from to 90.
Alessandro Sala (xela) updated the task description. (Show Details)
Alessandro Sala (xela) added a project: Add-ons (Community).
Alessandro Sala (xela) edited a custom field.
Alessandro Sala (xela) added a subscriber: Alessandro Sala (xela).
Alessandro Sala (xela) added a comment.Nov 15 2013, 10:05 PM

Sorry, I just realized that I submitted the bug report in the Addons section, but perhaps it should have been submitted in the BF Blender section (altough Cycles is technically an Addon)?

Alessandro

Brecht Van Lommel (brecht) lowered the priority of this task from 90 to Normal.Nov 15 2013, 10:07 PM
Brecht Van Lommel (brecht) edited projects, added BF Blender, Cycles; removed Add-ons (Community).
Brecht Van Lommel (brecht) changed the task status from Unknown Status to Unknown Status.Nov 15 2013, 10:10 PM
Brecht Van Lommel (brecht) claimed this task.

Unfortunately this is a known problem with no easy solution. By default Windows only lets the graphics card work on some task for 2 seconds, so if the scene is too complex and the GPU a relatively limited laptop GPU, this error can happen. Setting a smaller tile size can help, but it's not really reliable either.

More information here:
http://wiki.blender.org/index.php/Doc:2.6/Manual/Render/Cycles/GPU_Rendering#The_NVIDIA_OpenGL_driver_lost_connection_with_the_display_driver

We'd like to improve this at some point but for now it's not considered a bug, GPU rendering comes with some limitations.

Alessandro Sala (xela) added a comment.Nov 15 2013, 10:21 PM

Thank you for your answer Brecht.

I was aware of the GPU limitations, but I can't understand why it ONLY happens while rendering in the 3D view, and not while doing a full render with the same exact view.

If the problem is the limited performance of the GPU, shouldn't it happen every time I render the scene?

Alessandro

Brecht Van Lommel (brecht) added a comment.Nov 15 2013, 11:19 PM

It's confusing yes, but the 3D view render works in a somewhat different way than the final render which can influence this. In the 3D view everything stays on the GPU while in the final render it's loaded to the CPU.

Alessandro Sala (xela) added a comment.Nov 16 2013, 12:40 AM

Ok, thank you for the explanation.

Alessandro