Timeline for blender crashed twice during long render, how to detect and remedy reason for crash?
Current License: CC BY-SA 4.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 14, 2021 at 6:11 | history | edited | Sazerac |
removed bad tag
|
|
| Apr 13, 2021 at 22:08 | comment | added | S. Imp |
@NeverConvex I ran across a bug report here which was apparently resolved by using a different version of blender than the version installed using the Ubuntu Software installer (i.e. sudo apt install blender). The Ubuntu 20.04 default is Blender 2.82 (sub 7). I tried that same one-frame render command with Blender 2.92.0 downloaded from the Blender website and it rendered the problematic frame without complaint. I'm trying to render every frame now with the workaround and am optimistic.
|
|
| Apr 13, 2021 at 22:00 | comment | added | NeverConvex | I don't know anything material about the offending part of the cycles path-tracing engine, so am not sure what calculation is running into (I assume) precision issues internally to yield non-finite values, but a quick google turned up this post with a similar stacktrace: developer.blender.org/T76238 It suggests you might be able to avoid the crash by increasing the relevant number of light bounces. | |
| Apr 13, 2021 at 21:48 | history | edited | S. Imp | CC BY-SA 4.0 |
added single frame rendering failure detail
|
| Apr 13, 2021 at 21:26 | history | edited | S. Imp | CC BY-SA 4.0 |
added debug detail
|
| Apr 13, 2021 at 19:49 | history | asked | S. Imp | CC BY-SA 4.0 |