Search Issue Tracker
Won't Fix
Votes
0
Found in
2018.1.0a1
Issue ID
962829
Regression
No
[PLM] Memory leaks occur when switching baking backends
Steps for reproduction:
1) Download the project from the case 949121 or the link added below
2) Open the scene `ProgressiveLightmappingExample`
3) Bake the scene with Progressive Lightmapper
4) In Lighting window, switch the backend from `Progressive Lightmapper` to `Enlighten` and wait until lighting is re-generated.
5) Observe the memory leaks under Memory section of Global Maps tab of Lighting window
Notes:
- It doesn't occur when using simple scenes
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
- “Remove Unused Overrides” available on not loaded Scene and throws “ArgumentException: The scene is not loaded” warning
- Adaptive Probe Volume occlusion edge is calculated incorrectly when viewing probes near geometry edges
- Sampling a texture using an HLSL file throws shader errors and the code does not compile
- "Graphics.CopyTexture called with null source texture" error when Base Camera of an Overlay Camera is removed with DX11 Graphics API and Compatibility Mode enabled
- WebGL sends wrong value with large numbers when SendMessage function is used
Resolution Note:
Ideally there should be no need to switch baking pipelines repeatedly so I don't think this is a big problem in practice.
This issue has been identified as having low priority and has been closed without a fix. If the bug has no workaround and is blocking your production please feel free to reopen it with any additional information you might have. Sorry for the inconvenience this might cause.