render crash #47311

New Issue

Alexey · 2016-02-03T14:42:27+01:00

Alexey commented

2016-02-03 14:42:27 +01:00

System Information
Operating system and graphics card

Blender Version
Broken: (All)
Worked: (None)

Exact steps for others to reproduce the error
open this file, try to render - we will have crush(render will stop)
render.blend1

**System Information** Operating system and graphics card **Blender Version** Broken: (All) Worked: (None) **Exact steps for others to reproduce the error** open this file, try to render - we will have crush(render will stop) [render.blend1](https://archive.blender.org/developer/F279778/render.blend1)

Alexey commented

2016-02-03 14:42:27 +01:00

Changed status to: 'Open'

Alexey commented

2016-02-03 14:42:27 +01:00

Added subscriber: @Inwader77

Campbell Barton commented

2016-02-04 05:07:49 +01:00

Added subscriber: @ideasman42

Campbell Barton commented

2016-02-04 05:07:49 +01:00

At what percentage does the render crash? And what kind of crash to you get?

Can you turn down the complexity and still redo the crash (lower resolution, disable AA, disable, texturing, raytracing... etc... until you have a simpler file that still crashes).

Running this file in a debug build is very slow, its reached 70% and still processing, but no crash so far.

Also, please include information (os, blender version etc...)

At what percentage does the render crash? And what kind of crash to you get? Can you turn down the complexity and still redo the crash (lower resolution, disable AA, disable, texturing, raytracing... etc... until you have a simpler file that still crashes). Running this file in a debug build is very slow, its reached 70% and still processing, but no crash so far. Also, please include information (os, blender version etc...)

Alexey commented

2016-02-04 10:52:09 +01:00

In #47311#356152, @ideasman42 wrote:
At what percentage does the render crash? And what kind of crash to you get?

Can you turn down the complexity and still redo the crash (lower resolution, disable AA, disable, texturing, raytracing... etc... until you have a simpler file that still crashes).

Running this file in a debug build is very slow, its reached 70% and still processing, but no crash so far.

Also, please include information (os, blender version etc...)

this bug is active for all versions, include last version 50a19cc.
i don't know how to repeat it, if i was change anything in 3D view - render maybe properly.
if we switch off ray tracing - working properly, all other - not important. this scene is very simple.
CapturedMovie_converted.avi

System Information
windows7 64
ASUS ATI Radeon HD6870

Blender Version
Broken: (All)
Worked: (None)

> In #47311#356152, @ideasman42 wrote: > At what percentage does the render crash? And what kind of crash to you get? > > Can you turn down the complexity and still redo the crash (lower resolution, disable AA, disable, texturing, raytracing... etc... until you have a simpler file that still crashes). > > Running this file in a debug build is very slow, its reached 70% and still processing, but no crash so far. > > Also, please include information (os, blender version etc...) this bug is active for all versions, include last version 50a19cc. i don't know how to repeat it, if i was change anything in 3D view - render maybe properly. if we switch off ray tracing - working properly, all other - not important. this scene is very simple. [CapturedMovie_converted.avi](https://archive.blender.org/developer/F279913/CapturedMovie_converted.avi) ![1.png](https://archive.blender.org/developer/F279922/1.png) ![2.png](https://archive.blender.org/developer/F279923/2.png) System Information windows7 64 ASUS ATI Radeon HD6870 Blender Version Broken: (All) Worked: (None)

Brecht Van Lommel commented

2016-02-11 01:02:14 +01:00

Added subscriber: @brecht

Brecht Van Lommel commented

2016-02-11 01:02:14 +01:00

Changed status from 'Open' to: 'Archived'

Brecht Van Lommel closed this issue

2016-02-11 01:02:14 +01:00

Brecht Van Lommel self-assigned this 2016-02-11 01:02:14 +01:00

Brecht Van Lommel commented

2016-02-11 01:02:14 +01:00

To be clear, does Blender actually crash? Or does it hang and become unresponsive? Or is the render just really slow, but you can still cancel it?

From your last comment it seems it's just rendering really slow. The reason for that is that the "Substract" material has Depth set to 100 under Mirror, which Blender Internal just can't render efficiently. Just lower it to get render time under control again.

Blender Internal would need rendering algorithms like probabilistic splitting and Russian roulette to fix that, precisely the kind of things the Cycles shading system was designed for.

To be clear, does Blender actually crash? Or does it hang and become unresponsive? Or is the render just really slow, but you can still cancel it? From your last comment it seems it's just rendering really slow. The reason for that is that the "Substract" material has Depth set to 100 under Mirror, which Blender Internal just can't render efficiently. Just lower it to get render time under control again. Blender Internal would need rendering algorithms like probabilistic splitting and Russian roulette to fix that, precisely the kind of things the Cycles shading system was designed for.

Alexey commented

2016-02-11 15:07:19 +01:00

Depht is 2 only, not equal 100. this is hang and become unresponsive. i was set depth zero - i have this bug again.

Brecht Van Lommel commented

2016-02-11 21:00:57 +01:00

The "Substract" material on the floor has depth 100. The way the renderer works this means it will render up to a 100 bounces after that, potentially through the rest of the scene, regardless if other materials have a lower depth set.

If you can't cancel the render when it's stuck rendering very slowly, I can't reproduce that problem. Blender stays responsive for me, the render is just really slow.

The "Substract" material on the floor has depth 100. The way the renderer works this means it will render up to a 100 bounces after that, potentially through the rest of the scene, regardless if other materials have a lower depth set. If you can't cancel the render when it's stuck rendering very slowly, I can't reproduce that problem. Blender stays responsive for me, the render is just really slow.

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

render crash #47311