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
- Crash on JobQueue::HasJobGroupIDCompleted when closing the Editor while in Play mode on a specific project
- In "Preferences" section the “SpriteShape” menu item, the details page title “SpriteShape”, and “ControlPoint” entries are displayed as code strings rather than formatted UI strings
- Errors thrown constantly when Virtual Offset Debug is enabled and lighting was baked on AMD machine
- Persistent Memory Leak when reloading domain and using Distance-based Ghost Importance
- HDRP project doesn't render in standalone player when using High stripping
Add comment