Eevee: Blender crashes when rendering complex scenes with Stereoscopy and Motion Blur #88244

New Issue

Mircea Kitsune · 2021-05-13T01:37:04+02:00

Mircea Kitsune commented

2021-05-13 01:37:04 +02:00

System Information
Operating system: Linux-5.12.1-2-MANJARO-x86_64-with-glibc2.33 64 Bits
Graphics card: AMD Radeon (TM) R9 390 Series (HAWAII, DRM 3.40.0, 5.12.1-2-MANJARO, LLVM 11.1.0) AMD 4.6 (Core Profile) Mesa 21.0.3

Blender Version
Broken: version: 2.92.0, branch: makepkg (modified), commit date: 2021-02-24 16:25, hash: 02948a2cab
Worked: Unknown

Short description of error
When enabling Stereoscopy and producing a red-cyan anaglyph render in my Eevee scene, Blender will crash halfway through or near the end of rendering the frame, almost half of the time in total. Instead of a crash I occasionally get an interface glitch. After several attempts I noticed that Blender is also filling up my system RAM with a lot of cache memory, only freed up by using "echo 3 > /proc/sys/vm/drop_caches" in a console. Here is the /tmp/Blend.crash.txt log produced.

Blend.crash.txt

And here's a screenshot of the corrupted interface (default theme). Button textures and other GUI components occasionally disappear after a few renders if you avoid getting the crash: I can keep using Blender fine like this apparently, except stuff like checkboxes become invisible so I need to know where to click to toggle them.

Exact steps for others to reproduce the error
I tried producing a blend file I could share but was unable: The problem occurs in a larger and more complex scene with linked proxy characters, the crash goes away once I disable some collections. I'm unable to reproduce it in the default blend or even my simplified scene, and the full bundle isn't a project I can share here.

But I took some time to play with the objects and settings more in depth and found some clues: The crash disappears or becomes less likely when disabling rigged characters from the render, some of them with hair particles which may or may not be the culprit. It also seems to go away when I disable Motion Blur from the render settings. With both enabled though, the issue will always occur even in frames where no movement goes on and everything's static.

**System Information** Operating system: Linux-5.12.1-2-MANJARO-x86_64-with-glibc2.33 64 Bits Graphics card: AMD Radeon (TM) R9 390 Series (HAWAII, DRM 3.40.0, 5.12.1-2-MANJARO, LLVM 11.1.0) AMD 4.6 (Core Profile) Mesa 21.0.3 **Blender Version** Broken: version: 2.92.0, branch: makepkg (modified), commit date: 2021-02-24 16:25, hash: `02948a2cab` Worked: Unknown **Short description of error** When enabling Stereoscopy and producing a red-cyan anaglyph render in my Eevee scene, Blender will crash halfway through or near the end of rendering the frame, almost half of the time in total. Instead of a crash I occasionally get an interface glitch. After several attempts I noticed that Blender is also filling up my system RAM with a lot of cache memory, only freed up by using "echo 3 > /proc/sys/vm/drop_caches" in a console. Here is the /tmp/Blend.crash.txt log produced. [Blend.crash.txt](https://archive.blender.org/developer/F10088888/Blend.crash.txt) And here's a screenshot of the corrupted interface (default theme). Button textures and other GUI components occasionally disappear after a few renders if you avoid getting the crash: I can keep using Blender fine like this apparently, except stuff like checkboxes become invisible so I need to know where to click to toggle them. ![Screenshot_20210513_022607.png](https://archive.blender.org/developer/F10088999/Screenshot_20210513_022607.png) **Exact steps for others to reproduce the error** I tried producing a blend file I could share but was unable: The problem occurs in a larger and more complex scene with linked proxy characters, the crash goes away once I disable some collections. I'm unable to reproduce it in the default blend or even my simplified scene, and the full bundle isn't a project I can share here. But I took some time to play with the objects and settings more in depth and found some clues: The crash disappears or becomes less likely when disabling rigged characters from the render, some of them with hair particles which may or may not be the culprit. It also seems to go away when I disable Motion Blur from the render settings. With both enabled though, the issue will always occur even in frames where no movement goes on and everything's static.

Mircea Kitsune commented

2021-05-13 01:37:04 +02:00

Added subscriber: @MirceaKitsune

Richard Antalik commented

2021-05-13 22:52:08 +02:00

Added subscriber: @iss

Richard Antalik commented

2021-05-13 22:52:08 +02:00

Changed status from 'Needs Triage' to: 'Needs User Info'

Richard Antalik commented

2021-05-13 22:52:08 +02:00

Thank you for report but it is practically impossible for us to fix this issue unless we have a way to reproduce it.
You can try to simplify linked objects to the point that files become shareable. without these we really can't do much

Thank you for report but it is practically impossible for us to fix this issue unless we have a way to reproduce it. You can try to simplify linked objects to the point that files become shareable. without these we really can't do much

Mircea Kitsune commented

2021-05-17 23:14:00 +02:00

If it's the only way, I've started simplifying my scene and deleting my way toward the bare minimum needed to reproduce this crash. Main problem is the crash seems to rely on a linked character blend that's 100 MB large due to textures, and cherry on the top it's also NSFW (correct and detailed anatomy) so I need to see if I can edit that too so the team won't hate me. I believe it's CC0 licensed though so in this regard there should be no limitations: If the textures are required to reproduce the issue I'll post it in a place like mega.nz and share the link here if that's alright. Let me know what you recommend... in the meantime I'll work on simplifying the scene down to whatever keeps the crash going.

Also I can't help but share another screenshot: After a few renders during the simplification, the interface corrupted itself to the amount of drawing colored lines and triangles! What can possibly cause such an effect? Starting to worry this bug may be triggering something in the display driver... as an added note I have absolutely no issues with anything else, including games or rendering any other scene in Blender, this is the one and only circumstance that's doing it.

If it's the only way, I've started simplifying my scene and deleting my way toward the bare minimum needed to reproduce this crash. Main problem is the crash seems to rely on a linked character blend that's 100 MB large due to textures, and cherry on the top it's also NSFW (correct and detailed anatomy) so I need to see if I can edit that too so the team won't hate me. I believe it's CC0 licensed though so in this regard there should be no limitations: If the textures are required to reproduce the issue I'll post it in a place like mega.nz and share the link here if that's alright. Let me know what you recommend... in the meantime I'll work on simplifying the scene down to whatever keeps the crash going. Also I can't help but share another screenshot: After a few renders during the simplification, the interface corrupted itself to the amount of drawing colored lines and triangles! What can possibly cause such an effect? Starting to worry this bug may be triggering something in the display driver... as an added note I have absolutely no issues with anything else, including games or rendering any other scene in Blender, this is the one and only circumstance that's doing it. ![Screenshot_20210518_000936.png](https://archive.blender.org/developer/F10118998/Screenshot_20210518_000936.png)

Mircea Kitsune commented

2021-05-18 00:39:19 +02:00

Changed status from 'Needs User Info' to: 'Needs Triage'

Mircea Kitsune commented

2021-05-18 00:39:19 +02:00

Great news: I was able to do away with the textures and naughty bits on the model, bringing the whole thing down to just 5 MB as a zip. Here's a working test case with everything I suspect to be a contributor included.

Test.zip

Simply open Test.blend and press F12 to render: Everything is set up to reproduce the problem, I even set the sampling low so it won't take long per attempt. You may need to do so repeatedly, at times it happens on the first try while at other times it takes over 10 renders. When it happens you should either notice a crash or the interface corruption.

Great news: I was able to do away with the textures and naughty bits on the model, bringing the whole thing down to just 5 MB as a zip. Here's a working test case with everything I suspect to be a contributor included. [Test.zip](https://archive.blender.org/developer/F10119326/Test.zip) Simply open Test.blend and press F12 to render: Everything is set up to reproduce the problem, I even set the sampling low so it won't take long per attempt. You may need to do so repeatedly, at times it happens on the first try while at other times it takes over 10 renders. When it happens you should either notice a crash or the interface corruption.

Ankit Meel commented

2021-05-18 16:24:32 +02:00

Added subscriber: @ankitm

Ankit Meel commented

2021-05-18 16:24:32 +02:00

I rendered 5 times, albeit with 50% resolution because 100% froze the laptop for a minute or two (it recovered though.)
No crash or interface corruption, just laggy system which is understandable as GPU is busy.
macOS 10.14, Intel HD 6000 5e67dcf3d2

I rendered 5 times, albeit with 50% resolution because 100% froze the laptop for a minute or two (it recovered though.) No crash or interface corruption, just laggy system which is understandable as GPU is busy. macOS 10.14, Intel HD 6000 5e67dcf3d2

Ankit Meel commented

2021-05-18 17:21:00 +02:00

Changed status from 'Needs Triage' to: 'Needs User Info'

Ankit Meel commented

2021-05-18 17:21:00 +02:00

Actually the crash happens on blender 2.92 reliably, while none in the said hash above. So @MirceaKitsune could you test in 2.93 as well as 3.0 ? https://builder.blender.org/download/
crash18_05_2021.txt

Test.crash.txt

Actually the crash happens on blender 2.92 reliably, while none in the said hash above. So @MirceaKitsune could you test in 2.93 as well as 3.0 ? https://builder.blender.org/download/ [crash18_05_2021.txt](https://archive.blender.org/developer/F10123070/crash18_05_2021.txt) [Test.crash.txt](https://archive.blender.org/developer/F10123146/Test.crash.txt)

Mircea Kitsune commented

2021-05-18 17:22:08 +02:00

It only takes a few seconds for me but laptops don't have as powerful GPU's so that's understandable. I don't have Windows to test it there, but I wonder if this might be specific to AMD Linux users (Manjaro in my case). If anyone knows Linux people who use Blender especially with AMD graphics cards and the default FOSS driver (amdgpu on Mesa), please direct them to this bug and ask if they can help test as well.

Mircea Kitsune commented

2021-05-18 17:23:40 +02:00

Replied before seeing the last message. Glad it could be reproduced on 2.92, it's the latest release and what I use as well. Will test the newer versions and let you know if it goes away for me too.

Mircea Kitsune commented

2021-05-18 18:13:13 +02:00

Changed status from 'Needs User Info' to: 'Resolved'

Mircea Kitsune closed this issue

2021-05-18 18:13:13 +02:00

Mircea Kitsune self-assigned this 2021-05-18 18:13:13 +02:00

Mircea Kitsune commented

2021-05-18 18:13:13 +02:00

Did over a dozen renders in both my project and the simplified test posted here. So far I'm getting the same result as Ankit Meel: Whatever was causing it seems to be gone in 2.93.

In addition I'm also no longer getting random render results with odd variations: I was seeing some strange overlaps that looked like Z-fighting which varied between render attempts. That too only happened once I enabled stereoscopy: It was likely the same issue at its core, likely sometimes going wrong in the graphics data when multiple views are used.

I'm going to mark this as resolved given the next release should no longer produce it. If I notice the same problem in 2.93 or beyond I'll reopen.

Did over a dozen renders in both my project and the simplified test posted here. So far I'm getting the same result as Ankit Meel: Whatever was causing it seems to be gone in 2.93. In addition I'm also no longer getting random render results with odd variations: I was seeing some strange overlaps that looked like Z-fighting which varied between render attempts. That too only happened once I enabled stereoscopy: It was likely the same issue at its core, likely sometimes going wrong in the graphics data when multiple views are used. I'm going to mark this as resolved given the next release should no longer produce it. If I notice the same problem in 2.93 or beyond I'll reopen.

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

Eevee: Blender crashes when rendering complex scenes with Stereoscopy and Motion Blur #88244