Search Issue Tracker
Fixed
Fixed in 2020.3.45f1, 2021.3.18f1, 2022.2.4f1, 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
- [HDRP] Game view renders artifacts when Camera's Component "Post Anti-aliasing" is set to "TAA" and Dynamic Resolution's "Forced Screen Percentage" is changed
- A deactivated Prefab's name color becomes white when a GameObject in the scene is deactivated
- The Game view becomes blank when using Frame Debugger with MSAA and Texture binding enabled in Play Mode
- Crash on dynamixel_sdk.dynamixel:groupSyncReadTxRxPacket when entering Play Mode after updating path to Dynamixel SDK in script
- NullReferenceException is thrown when changing the Inspector preview selection
Add comment