Crash Rendering (Cycles/Cuda) #44222

New Issue

B-Lee · 2015-04-01T20:31:32+02:00

B-Lee commented

2015-04-01 20:31:32 +02:00

System Information
Window 7 64-bit and Nvidia GeForce GTX 760

Blender Version
Broken: 2.74

Short description of error

A simple nodes setup shown on the top part of the image, with GPU rendering in both F12 or viewport render, it happen to be crash as shown at the bottom part of the image.
Tested with CPU render in viewport render mode, when adjusting/draging the ColorRamp node gradient bar, it having some stall/freeze situation for more or less of a second.

**System Information** Window 7 64-bit and Nvidia GeForce GTX 760 **Blender Version** Broken: 2.74 **Short description of error** A simple nodes setup shown on the top part of the image, with GPU rendering in both F12 or viewport render, it happen to be crash as shown at the bottom part of the image. Tested with CPU render in viewport render mode, when adjusting/draging the ColorRamp node gradient bar, it having some stall/freeze situation for more or less of a second. ![Bug_01.jpg](https://archive.blender.org/developer/F157117/Bug_01.jpg)

B-Lee commented

2015-04-01 20:31:32 +02:00

Changed status to: 'Open'

B-Lee self-assigned this 2015-04-01 20:31:32 +02:00

B-Lee commented

2015-04-01 20:31:32 +02:00

Added subscriber: @toki46-3

Aaron Carlisle commented

2015-04-01 21:34:03 +02:00

Added subscriber: @Blendify

Aaron Carlisle commented

2015-04-01 21:34:04 +02:00

We need a bit more information from you so let me give you some homework:

Information about what kind of operating system and graphics card you use might be helpful
Try the latest build from our buildbot .(Not Gooseberry)
Ensure both your OS and drivers are fully up-to-date
For Windows 7, at least Service Pack 1 is mandatory, please ensure it is installed on your machine.
Ensure you have installed MSVC2013 redistributable package .
Try to disable any running antivirus.
Ensure you have no python executable available in your %path% envvar.
Try to re-download and re-install Blender.
Try to start Blender in factory settings (--factory-startup commandline option) (this will ensure whether this is a userpref or addon issue or not).
If you are using Win7, Try to place this dll next to your blender.exe (software OGL, will be slow, but will show whether this is a driver issue or not).
(and again, more or less copied & pasted from Bastien)

Think that's enough for now... ;)

(Copied from Julian :)

We need a bit more information from you so let me give you some homework: * Information about what kind of operating system and graphics card you use might be helpful * Try the latest build from our [buildbot ](https://builder.blender.org/download/).(**Not Gooseberry**) * Ensure both your OS and drivers are fully up-to-date * For Windows 7, at least Service Pack 1 is mandatory, please ensure it is installed on your machine. * Ensure you have installed [MSVC2013 redistributable package ](http://www.microsoft.com/en-us/download/details.aspx?id=40784). * Try to disable any running antivirus. * Ensure you have no python executable available in your %path% envvar. * Try to re-download and re-install Blender. * Try to start Blender in factory settings (--factory-startup commandline option) (this will ensure whether this is a userpref or addon issue or not). * If you are using Win7, Try to place [this dll ](http://download.blender.org/ftp/sergey/softwaregl/win64/opengl32.dll) next to your blender.exe (software OGL, will be slow, but will show whether this is a driver issue or not). (and again, more or less copied & pasted from Bastien) Think that's enough for now... ;) (Copied from Julian :)

B-Lee was unassigned by Aaron Carlisle

2015-04-01 21:34:34 +02:00

Krzysztof Rećko commented

2015-04-01 22:33:55 +02:00

Added subscriber: @chrisr

Krzysztof Rećko commented

2015-04-01 22:33:55 +02:00

Hey, I can confirm this bug.

I have Win7 64, SP1, Nvidia GTX 560Ti, driver 347.88 (17 March).
Latest buildbot, and my own build from latest master both have this.
Check!
Check!
Check!
Check!
Check!
Check!
Check!
Check!

Here is a file I ended up creating: bug.blend. To reproduce the bug: Set device to CUDA, F12 to render -> exact same error as @toki46-3 had and complete blender crash.
Listing from console after the bug:

CUDA error: Unknown error in cuCtxSynchronize()

Refer to the Cycles GPU rendering documentation for possible solutions:
http://www.blender.org/manual/render/cycles/gpu_rendering.html

CUDA error: Unknown error in cuMemcpyDtoH((uchar*)mem.data_pointer + offset, (CUdeviceptr)(mem.device_pointer + offset), size)
CUDA error: Unknown error in cuMemcpyDtoH((uchar*)mem.data_pointer + offset, (CUdeviceptr)(mem.device_pointer + offset), size)
CUDA error: Unknown error in cuMemFree(cuda_device_ptr(mem.device_pointer))
CUDA error: Unknown error in cuMemFree(cuda_device_ptr(mem.device_pointer))
CUDA error: Unknown error in cuMemAlloc(&device_pointer, size)
CUDA error: Unknown error in cuMemAlloc(&device_pointer, size)
(...) - around 264 of these
CUDA error: Unknown error in cuMemAlloc(&device_pointer, size)
CUDA error: Unknown error in cuMemAlloc(&device_pointer, size)
CUDA error: Unknown error in cuMemFree(cuda_device_ptr(mem.device_pointer))
CUDA error: Unknown error in cuMemFree(cuda_device_ptr(mem.device_pointer))
(...) - around 18 of these
CUDA error: Unknown error in cuMemFree(cuda_device_ptr(mem.device_pointer))
CUDA error: Unknown error in cuMemFree(cuda_device_ptr(mem.device_pointer))
AL lib: (EE) alc_cleanup: 1 device not closed

Hey, I can confirm this bug. - I have Win7 64, SP1, Nvidia GTX 560Ti, driver 347.88 (17 March). - Latest buildbot, and my own build from latest master both have this. - Check! - Check! - Check! - Check! - Check! - Check! - Check! - Check! Here is a file I ended up creating: [bug.blend](https://archive.blender.org/developer/F157197/bug.blend). To reproduce the bug: Set device to CUDA, F12 to render -> exact same error as @toki46-3 had and complete blender crash. Listing from console after the bug: ``` CUDA error: Unknown error in cuCtxSynchronize() Refer to the Cycles GPU rendering documentation for possible solutions: http://www.blender.org/manual/render/cycles/gpu_rendering.html CUDA error: Unknown error in cuMemcpyDtoH((uchar*)mem.data_pointer + offset, (CUdeviceptr)(mem.device_pointer + offset), size) CUDA error: Unknown error in cuMemcpyDtoH((uchar*)mem.data_pointer + offset, (CUdeviceptr)(mem.device_pointer + offset), size) CUDA error: Unknown error in cuMemFree(cuda_device_ptr(mem.device_pointer)) CUDA error: Unknown error in cuMemFree(cuda_device_ptr(mem.device_pointer)) CUDA error: Unknown error in cuMemAlloc(&device_pointer, size) CUDA error: Unknown error in cuMemAlloc(&device_pointer, size) (...) - around 264 of these CUDA error: Unknown error in cuMemAlloc(&device_pointer, size) CUDA error: Unknown error in cuMemAlloc(&device_pointer, size) CUDA error: Unknown error in cuMemFree(cuda_device_ptr(mem.device_pointer)) CUDA error: Unknown error in cuMemFree(cuda_device_ptr(mem.device_pointer)) (...) - around 18 of these CUDA error: Unknown error in cuMemFree(cuda_device_ptr(mem.device_pointer)) CUDA error: Unknown error in cuMemFree(cuda_device_ptr(mem.device_pointer)) AL lib: (EE) alc_cleanup: 1 device not closed ```

perfection cat commented

2015-04-02 03:49:30 +02:00

Added subscriber: @sindra1961

perfection cat commented

2015-04-02 03:49:30 +02:00

I seem to require a large quantity of memory.

B-Lee commented

2015-04-02 06:45:24 +02:00

Windows 7 64bit SP1, Nvidia GeForce GTX 760 (driver ver: 347.88) latest driver release date: 3/17/2015
Windows 64 bit Official blender-2.74-4b84759-win64.zip
Check
Check
Check
Check
Check
Check
Check
Check

After doing all above, new test with latest buildbot is still the same, only difference is blender still operate instead of totally crash.
Here are both viewport render and F12 render test.

- Windows 7 64bit SP1, Nvidia GeForce GTX 760 (driver ver: 347.88) latest driver release date: 3/17/2015 - Windows 64 bit Official blender-2.74-4b84759-win64.zip - Check - Check - Check - Check - Check - Check - Check - Check After doing all above, new test with latest buildbot is still the same, only difference is blender still operate instead of totally crash. Here are both viewport render and F12 render test. ![Bug_2.jpg](https://archive.blender.org/developer/F157401/Bug_2.jpg)

Antonis Ryakiotakis commented

2015-04-02 20:02:29 +02:00

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

Antonis Ryakiotakis commented

2015-04-02 20:02:29 +02:00

@Blendify, this is only to be copied in certain bugs that look like OpenGL failures or crashes that cannot be reproduced by others. It's good that you want to help, but the best way users can help is by confirming that a bug occurs for them. Generally merging tasks and such replies should be done by developers (who can evaluate if something really is a bug in our code or not, in which case we check for crappy drivers etc).

And finally, summoning @ThomasDinges or @Sergey here to take a look.

At reporter: A blend file is -always- better than a picture and means we are on the same page - which is often not the issue if we try to recreate the file here.

@Blendify, this is only to be copied in certain bugs that look like OpenGL failures or crashes that cannot be reproduced by others. It's good that you want to help, but the best way users can help is by confirming that a bug occurs for them. Generally merging tasks and such replies should be done by developers (who can evaluate if something really is a bug in our code or not, in which case we check for crappy drivers etc). And finally, summoning @ThomasDinges or @Sergey here to take a look. At reporter: A blend file is -always- better than a picture and means we are on the same page - which is often not the issue if we try to recreate the file here.

Aaron Carlisle commented

2015-04-03 19:38:22 +02:00

Well since the picture shows a crashing driver it was probably a good idea

Campbell Barton changed title from ~~Blender Crash~~ to Crash Rendering (Cycles/Cuda)

2015-04-06 05:35:09 +02:00

Sergey Sharybin self-assigned this 2015-04-06 09:47:15 +02:00

Sergey Sharybin commented

2015-04-06 09:47:15 +02:00

Pointiness is a surface attribute, can't really be used for volume. But crash should not happen as well. Will have a look into this.