Search Issue Tracker
In Progress
In Progress in 6000.2.X
Under Consideration for 6000.0.X, 6000.1.X, 6000.3.X
Votes
0
Found in
6000.0.47f1
6000.1.0b15
6000.2.0a9
6000.3.0a1
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
- The tag adder functionality does not work if a space is entered instead of a name
- Errors thrown in the Console when configuring In-App Purchases package
- Longer Scaler Profile names go out of the"Scaler Profilers" section
- AI Navigation window UI elements overlap when the AI Navigation window is docked and resized
- Editor freezes after some time when using NavMeshQuery::Raycast
Add comment