Search Issue Tracker
Fixed in 2020.3.45f1
Fixed in 2020.3.X, 2021.3.X, 2022.2.X, 2023.1.X, 2023.1.0a25
Votes
0
Found in
2020.3.41f1
2021.3.13f1
2022.1.22f1
2022.2.0b14
2023.1.0a18
Issue ID
UUM-18684
Regression
No
Memory usage slowly rises overtime when LightProbes.Tetrahedralize is enabled
Reproduction steps:
1. Open the attached project “IN-19550_NewRepro.zip“
2. Open Task Manager
3. In the Editor enter Play Mode and observe the memory usage
4. Exit Play Mode
5. In the Hierarchy window select the “Test“ GameObject and select “Enable Tetrahedralize“ in the Inspector window
6. Enter Play Mode
7. Observe the memory usage in the Task Manager
Expected result: The memory usage of the Editor is similar whether Tetrahedralize is enabled or not
Actual result: The memory usage slowly rises overtime implying that there is a memory leak
Reproducible with: 2020.3.41f1, 2021.3.13f1, 2022.1.22f1, 2022.2.0b14, 2023.1.0a18
Reproduced on: Windows 10 Pro
Note: Also reproduced in Player
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Redoing creation of Sub Scenes and Cube GameObjects in Hierarchy throws “Assertion failed on expression: 'targetScene != nullptr’” error in Console window
- Selecting “New Sub Scene” after assigning “New Scene” in Sub Scene Script Component throws “Destroying GameObjects immediately is not permitted” in the Console window
- Shader Graph "Zoom Step Size" can be set to 0 even though the zoom still works
- Enabling/Disabling the Deprecated Nodes doesn't apply to the opened Shader Graph unless any Variable is added to the Blackboard
- Group Selection title text size is smaller in renaming than the actual font size
Add comment