Crash after rendering large scene
Open, NormalPublic

Description

System Information
Windows 10, GTX 1080Ti & 660Ti

Blender Version
Broken: 2.80 Alpha 2 a421cfa8d31 (today's build)

Short description of error
Blender crashes after finishing rendering in Cycles (status says 'Finished', but before the compositing kicks in). I changed a lot of settings between renders (motion blur, persistent images, added vector pass, removed diffuse pass, turned off cryptomatte), but even after reverting the changes the crash still occurs.

Exact steps for others to reproduce the error
Open the file
Render the scene as-is

Update: Blender also crashes if I try to delete the tree objects or collection. So far I haven't been able to narrow it down any farther.

I'm not able to reproduce this from scratch, but if I import everything into a new file I still get a crash.


File: https://www.dropbox.com/s/3tvwi2835c4qjtm/bulldozer_03_error.blend?dl=0

Details

Type
Bug
Philipp Oeser (lichtwerk) triaged this task as Normal priority.Fri, Nov 9, 3:09 PM

That one is too memory hungry for my machine :)

@Brecht Van Lommel (brecht): maybe someone can check on one of the studio machines?

Ok, after digging into this more I narrowed down the issue. I think it has less to do with Cycles rendering and more to do with materials. @Philipp Oeser (lichtwerk) Here's a scene with just the tree assets that should run on any machine. They have no modifiers, no particle systems, and are not really that dense of meshes. However, blender will immediately crash if you head to the materials tab in the properties editor.

Another clue is that viewport rendering works like a charm in both Eevee and Cycles, but a final render in either engine will cause a crash.