Search Issue Tracker
Duplicate
Votes
1
Found in
5.6.0f3
Issue ID
897559
Regression
No
Progressive Lightmapper - extremely high RAM usage, memory is not released
Steps to reproduce:
1. Open attached project
2. Go to lighting -> scene
3. Make sure that stationary lighting is set to progressive
4. Turn on Auto-Generate
5. Observe the rising RAM usage in the task manager
Expected result: Progressive lightmapper RAM usage should not be this high, memory should be released
Reproduced in: 2017.1.0a6, 2017.1.0a4, 5.6.0f3, 5.6.0b6
-
Trepidation
Aug 30, 2017 18:24
Unity's Progressive lightmapper tries to use over 32GB of memory (runs out of memory on my machine at that point), on the Blacksmith Bridge scene from Unity. Who the hell has that much memory?
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Editor crashes on StoredGraphicsBuffer::GetGfxBufferID when VFX Graph property is modified during Play Mode and Application.targetFrameRate is used to limit FPS
- Crash on NVAPI_Thunk when changing Player resolution while HDR display is used and Direct3D12 is set as the graphics API
- Only one out of multiple cameras is shown in the Play Mode while HDR display is used and Direct3D12 is set as the graphics API
- The "Paste Component as New" option is incorrectly displayed as active despite the action being prohibited
- "TLS Allocator ALLOC_TEMP_TLS" errors are thrown when unsuccessfully importing an FBX file
This is a duplicate of issue #1204993