Blender crashes direct after hitting render button (window closes whithout any warning) Render with cycles is a matter of luck #47500

New Issue

Niels · 2016-02-20T02:09:53+01:00

Niels commented

2016-02-20 02:09:53 +01:00

System Information
Windows 7
nvidia GTX 970
Intel 4,00Ghz Quad core i7
see text file for further information

Blender Version
Broken: 2.75a, 2.76 (no further versions tested)

Short description of error

after making a test scene with a medium complex material without image textures, doesn't matter what kind of material: it also can be fancy glass or simple abs-plastic (see blend file!)
light comes from an SMALL(10 MB) hdr image, which fits definately in my Vram of my graphics card (4GB) - USED PLUGIN: Pro Lighting skies from blenderguru (but this cannot be the problem, i've tested it without and it crashes)
the render engine is cycles (of course ;)
all build in plugins are enabled

THE CRITICAL PART: HITTING THE RENDER BUTTON

it's crashes very randomly, the first hit on the render button is mostly successful but the next render crashes very often
(window closes and is disappeared, whithout any warning)
even after restarting the computer, switch to CPU mode, reduce the light bounces..... the problem is still existing!

Here is the error message (i was able to take the Screenshot in a few milliseconds :D )
Couldn't unmap memory
Error: EXCEPTION_ACCESS_VIOLATION

(I assume, that i have enough RAM, VRAM and SSD storage even with 6GB left an a 120GB SSD)

Blend file and system information
{F284031}Material_Test.blend

**System Information** Windows 7 nvidia GTX 970 Intel 4,00Ghz Quad core i7 see text file for further information **Blender Version** Broken: 2.75a, 2.76 (no further versions tested) **Short description of error** - after making a test scene with a medium complex material without image textures, doesn't matter what kind of material: it also can be fancy glass or simple abs-plastic (see blend file!) - light comes from an SMALL(10 MB) hdr image, which fits definately in my Vram of my graphics card (4GB) - USED PLUGIN: Pro Lighting skies from blenderguru (but this cannot be the problem, i've tested it without and it crashes) - the render engine is cycles (of course ;) - all build in plugins are enabled THE CRITICAL PART: HITTING THE RENDER BUTTON it's crashes very randomly, the first hit on the render button is mostly successful but the next render crashes very often (window closes and is disappeared, whithout any warning) even after restarting the computer, switch to CPU mode, reduce the light bounces..... the problem is still existing! **Here is the error message (i was able to take the Screenshot in a few milliseconds :D )** Couldn't unmap memory Error: EXCEPTION_ACCESS_VIOLATION ![Unbenannt.png](https://archive.blender.org/developer/F284033/Unbenannt.png) (I assume, that i have enough RAM, VRAM and SSD storage even with 6GB left an a 120GB SSD) **Blend file and system information** {[F284031](https://archive.blender.org/developer/F284031/system-info.txt)}[Material_Test.blend](https://archive.blender.org/developer/F284032/Material_Test.blend)

Niels commented

2016-02-20 02:09:54 +01:00

Changed status to: 'Open'

Niels commented

2016-02-20 02:09:54 +01:00

Added subscriber: @mrnick1994

Thomas Dinges commented

2016-02-20 10:25:56 +01:00

Added subscriber: @ThomasDinges

Thomas Dinges commented

2016-02-20 10:25:56 +01:00

Please test with Testbuild 2: http://download.blender.org/release/Blender2.77/

Niels commented

2016-02-20 12:32:51 +01:00

okay, i've tested the version 2.73 and 2.77.
same problem!

disabled all unneccesary addons and hit render a couple times in the standard scene.
everything was fine.

then i have loaded the test scene with materials and it crashes again at the first try.

i've found something interesting in the console:

okay, i've tested the version 2.73 and 2.77. same problem! disabled all unneccesary addons and hit render a couple times in the standard scene. everything was fine. then i have loaded the test scene with materials and it crashes again at the first try. i've found something interesting in the console: ![screenshot2.png](https://archive.blender.org/developer/F284191/screenshot2.png)

Niels commented

2016-02-20 12:43:15 +01:00

the weird thing is, that i also had this problem on 2 other iMacs with other blend-files.
it crashes not so often, but the chance is there.

maybe its a problem with a specific basic shader node with a particular setting?

the weird thing is, that i also had this problem on 2 other iMacs with other blend-files. it crashes not so often, but the chance is there. maybe its a problem with a specific basic shader node with a particular setting?

Brecht Van Lommel commented

2016-02-21 19:48:12 +01:00

Added subscriber: @brecht

Brecht Van Lommel commented

2016-02-21 19:48:12 +01:00

I've been trying to reproduce crashes with this file using a GTX 960 on Windows 10, but so far I found no problems.

Looking at the world nodes, there are about 150 node groups and 300 images used. Not sure how they got there, but I doubt that was intentional. It would be good if you could tests rendering with all those unnecessary node groups removed, to see if that's related.

If the node group is unused, then I don't think the image will actually be loaded. But still it would be useful to look at the memory usage in the Windows task manager while it's rendering, to see if it's running out of memory. The error message seems like an error that might happen when running out of memory.

I've been trying to reproduce crashes with this file using a GTX 960 on Windows 10, but so far I found no problems. Looking at the world nodes, there are about 150 node groups and 300 images used. Not sure how they got there, but I doubt that was intentional. It would be good if you could tests rendering with all those unnecessary node groups removed, to see if that's related. If the node group is unused, then I don't think the image will actually be loaded. But still it would be useful to look at the memory usage in the Windows task manager while it's rendering, to see if it's running out of memory. The error message seems like an error that might happen when running out of memory.

lvxejay commented

2016-02-22 16:30:18 +01:00

Added subscriber: @lvxejay

lvxejay commented

2016-02-22 16:30:18 +01:00

Do you have any settings enabled in the Color Management tab? If you are using Film, RRT, Log, or Raw color management settings, or have color curves enabled, or you are using one of the built in camera filters, Blender will crash upon rendering your scene. (These settings can be found in Scene Properties, next to the World Properties button, underneath the Color Management tab)

Niels commented

2016-02-22 20:27:01 +01:00

hi,

unfortunately, i can test this on friday at the earliest.

thank you so far for helping me out!
it's great to talk directly with the developers, who make this great piece of software better ;)
...
i'll donate some money to the blender foundation ;)

thanks :)

hi, unfortunately, i can test this on friday at the earliest. thank you so far for helping me out! it's great to talk directly with the developers, who make this great piece of software better ;) ... i'll donate some money to the blender foundation ;) thanks :)

NikoLeopold commented

2016-02-26 00:06:55 +01:00

Added subscriber: @NikoLeopold

Niels commented

2016-02-26 21:43:16 +01:00

Added subscriber: @jared-2

Niels commented

2016-02-26 21:43:16 +01:00

Hey,

i've tested now the possible solutions:

@brecht
I deleted the uneccesary world nodes and opened the task manager.
then i've started the render process, the window closes immediately as expected.

the ram shows normal behavior, the ram load goes down a little bit when the window closes.
so
nothing unusual.

@jared-2
I haven't changed the settings there.
additionally, i've test it with some settings (add a film look, change the color spaces)

nothing changed. :(

so
I open the console and found this.
maybe, there is something wrong with the python software?

Hey, i've tested now the possible solutions: @brecht I deleted the uneccesary world nodes and opened the task manager. then i've started the render process, the window closes immediately as expected. the ram shows normal behavior, the ram load goes down a little bit when the window closes. so nothing unusual. @jared-2 I haven't changed the settings there. additionally, i've test it with some settings (add a film look, change the color spaces) nothing changed. :( so I open the console and found this. maybe, there is something wrong with the python software? ![screenshot3.png](https://archive.blender.org/developer/F285970/screenshot3.png)

Niels commented

2016-02-26 22:05:06 +01:00

...
PROBLEM SOLVED

I disabled all addons again and hit the render button.
now
the renderer doesn't crash!!!!

then I enabled all addons step by step to see, if something causes the problem.
all addons were enabled, and blender runs stable.

maybe it was a combination of uneccesary world nodes and too much addons? :D

... PROBLEM SOLVED I disabled all addons again and hit the render button. now the renderer doesn't crash!!!! then I enabled all addons step by step to see, if something causes the problem. all addons were enabled, and blender runs stable. maybe it was a combination of uneccesary world nodes and too much addons? :D

Niels commented

2016-02-27 11:48:48 +01:00

ahhhh
okay :D

it's the pro lighting sky addon, which causes the problem.
i've enabled it and connected to the world output in the node editor and it stops working again. -.-

maybe it's not the right place here for 3rd party addons here, is it?

ahhhh okay :D it's the pro lighting sky addon, which causes the problem. i've enabled it and connected to the world output in the node editor and it stops working again. -.- maybe it's not the right place here for 3rd party addons here, is it?

Thomas Dinges commented

2016-02-27 11:55:06 +01:00

Changed status from 'Open' to: 'Archived'

Thomas Dinges closed this issue

2016-02-27 11:55:06 +01:00

Thomas Dinges self-assigned this 2016-02-27 11:55:06 +01:00

Thomas Dinges commented

2016-02-27 11:55:06 +01:00

Please report this issue to the Addon author then. We need clear and reproducable cases here, and issues with third party addons cannot be fixed here.

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 crashes direct after hitting render button (window closes whithout any warning) Render with cycles is a matter of luck #47500