Corrupt scene file after out-of-memory?

Hi all,

Thanks in advance for any insight you might be able to provide here - I’m working on a fairly large scene file, in excess of 100m triangles. I have a fairly beefy system with 32GB of VRAM and 128GB of system RAM.

When attempting to render just now, I experienced some sort of crash - Blender stopped responding, and displayed this:

Any further attempt to render the scene results in the same - the interface responds, and I can navigate the scene, but, it’s…this.

My system can definitely handle it (performance overlay screenshot) so I’m wondering what happened here?

I created a new .blend file, and Appended the geometry of the buildings I wanted, but I then found that ANY object which had a material that had a texture map/file applied to it was rendering the same pink you see in the screenshot above, and attempting to manually re-link the texture paths didn’t work: the materials themselves were totally corrupted, and I had to delete them from the Blender file and manually append them from my library.

Anyone have any idea what’s going on here, and how to stop it in the future?

Since you already reworked the scene it’s too late this time, however you can try restoring from last session or autosave next time a crash happens. This may save some time :slight_smile:

Yeah, that’s how I got the scene file back - but all of the materials were corrupted even in the autosave, like I mentioned above :upside_down_face: