Page MenuHome

Evee Render crashes [2.80] Beta
Confirmed, NormalPublicKNOWN ISSUE


System Information
Operating system: Win10
Graphics card: 980ti
32GB memory

Blender Version
2.80 2019-02-10

Short description of error
Hard disk storage overflow occurring

Exact steps for others to reproduce the error
Particle simulations

1000's particles
over 10's of thousands frames

It seems Evee renderer is built around rendering baking viewport to file, in certain situations auto saving a large temporary baked file leads to a system running out of memory when the file exceeds available storage with large bakes.

Autosaves with large bakes to any available memory on this, this can be replicated with high memory commit states.

I also suspect when the memory commit exceeds the remaining memory on the computer, saving attempts to write to disk and subsequently crashes a number of background programs whose telemetry attempts to use disk space to hash the reports.
The target file attempting to be saved is corrupted if it is being overwritten.
I haven't confirmed whether the project file or autosave file corrupts in the process of saving, but it is very easy to lose a project and or backup when the bake commit is disproportion large to available memory on the machine.

autosave : Enabled (default 2min)

Event Timeline

Sebastian Parborg (zeddb) lowered the priority of this task from 90 to 30.Feb 21 2019, 4:15 PM

You have only posted a description of the error not any steps to reproduce.

Please also always test with the latest blender beta before reporting issues in the off chance that this has already been fixed.

Large(ish) memory commits in some instances can quickly overwrite all remaining disk space

You have still not provided detailed steps or a minimal .blend file so it is easy to reproduce the problem.

Please follow our submission template and guidelines and make a complete, valid bug report, with required info, precise description of the issue, precise steps to reproduce it, small and simple .blend and/or other files to do so if needed, etc.

A guideline for making a good bug report can be found here:

If you don't understand it, don't worry about undertaking it.

I'm saying Evee has no preventative safeguards in terms of memory runaway. Viewport cache could be baked to a separate scaleable temporary file, separate from project autosave in order to prevent complete loss of project in "high" resource scenarios. Color coordinated resources usage could be a welcome addition but unnecessary

High resource projects in some situations with evee viewport *will* result in unexpected project loss and crashes with autosave

Sebastian Parborg (zeddb) raised the priority of this task from 30 to Normal.
Richard Antalik (ISS) changed the subtype of this task from "Report" to "Known Issue".