Search Issue Tracker
Active
Under Consideration for 6000.0.X, 6000.1.X, 6000.2.X
Votes
0
Found in
6000.0.47f1
6000.1.0b15
6000.2.0a9
Issue ID
UUM-103088
Regression
Yes
Mono Memory not being released when instantiating and destroying objects using WebGL
Steps to reproduce:
1. Open the attached “CleanProj_6000.0.zip” project
2. Build the project for WebGL
3. Observe the Mono memory in the build
Expected result: After the assets are removed, the Mono memory decreases
Actual result: After the assets are removed, the Mono memory stays the same
Reproducible in: 6000.0.0b12, 6000.0.47f1, 6000.1.0b15, 6000.2.0a9
Not reproducible in: 2022.3.61f1, 2023.1.0b1
Couldn’t test in: 2023.2.0a1, 6000.0.0b11 (because of build errors)
Reproducible on: Windows 10, Windows 11
Not reproducible on: No other environment tested
Note: After some time it throws an OOM error
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- "Create Empty Child" Option Creates Root Object When No Parent Is Selected
- Freeze/Crash when entering Play Mode in a specific project
- Lack of documentation regarding VFX Ray Tracing support
- Shader properties do not appear on the GameObject when switching ShaderGraphs during runtime in the Player
- Multiple '-' symbols are allowed to appear in a row when inputting '.' into a non-decimal numeric field
Add comment