Search Issue Tracker
Fixed in 2020.1.X
Duplicate in 2019.2.X, 2019.3.X
Fixed in 2018.4.X
Votes
0
Found in
2019.1.0a11
Issue ID
1178584
Regression
Yes
Progressive lightmapper leaks memory upon subsequent scene switches and bakes
Steps to reproduce:
1. Download and open the attached project
2. Navigate to Assets > Scenes and open SampleScene 1
3. Wait for the lighting to bake
4. Navigate to Lighting Settings > Baked Lightmaps tab ant take note of the value in the Leaks section
5. Repeat steps 2-4 for the rest of the scenes
6. Notice, how the has increased upon subsequent bakes
Notes:
- Reproduces in all versions of from 2019.1.0a11 and onward
- Reproduces both with CPU and GPU PLM
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