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
Comments (1)
-
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
- Crash on [NSApplication endModalSession:] when saving while Play Mode is loading
- Incorrect Preferred Height calculation when a single text line uses different Font Assets
- [ShaderGraph] Redo Collapse Nodes action does not fully collapse the Nodes
- [Ubuntu] Mouse cursor is set box select mode after exiting VFX Graph's Rename Context function
- Unrecognized identifier DECLARE_STACK_CB error is thrown when VirtualTexture Property is used with Custom RenderTexture target
This is a duplicate of issue #1204993