Search Issue Tracker
Not Reproducible
Votes
3
Found in
5.2.1p1
Issue ID
734329
Regression
No
Unity crashes when running out of ram when baking lighting
To reproduce:
1. Open attached project
2. Open scene "CastleCoaster"
3. Build lighting
One of the threads will slowly (in 10-15 min.) eat up the available RAM until there is almost none left, then RAM usage will stay at 94-99% for 10-15 minutes, a few errors will be thrown (Failed executing external process for 'Clustering' job.) after which Unity will crash, with some other results, such as:
-Resetting the desktop wallpaper
-Changing the resolution to the smallest possible
-Crashing the graphics card
-Crashing other applications
Expected result: Unity doesn't crash, or at the very least doesn't produce the mentioned effects and displays a message explaining that it crashed because it ran out of RAM.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Add comment