Search Issue Tracker
Fixed
Fixed in 2022.3.10f1
Votes
1
Found in
2022.3.7f1
Issue ID
UUM-46520
Regression
Yes
Leaking dynamically created meshes when cloning UXML items to a UI Document every frame
Reproduction steps:
1. Open project “2022.2_BugReport.zip”
2. Open “SampleScene”
3. Enter Play Mode
4. Open “Window\Analysis\Profiler” and observe “Memory\Mesh Memory”
Expected result: Mesh Memory is not rising
Actual result: Mesh Memory is rising
Reproducible with: 2022.2.0a9, 2022.3.7f1, 2023.1.0a19
Not reproducible with: 2021.3.29f1, 2022.2.0a8, 2023.1.9f1, 2023.2.0b5
Fixed in: 2023.1.0a20
Reproducible on: macOS Ventura 13.2.1 (Intel), Windows 11 (by the reporter)
Not reproducible on: No other environment tested
Notes:
- Unchecking the “Leak On\Off” checkbox in Game view stops Mesh Memory from rising
- Also reproducible in Standalone Player
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
- [Android] Error "Blitter is already initialized" is present when Adaptive Probe Volumes are used with OpenGLES3
- VFX Graph effect instance stops rendering when a second instance of the same effect starts 2 frames later
- Operations on the Color32 array are not reflected in WebGL Player when HDR is off
- Rigidbody moves away from the original GameObject when Center of Mass is set in every frame
- WebGL Player does not proceed beyond logo screen when "Target WebAssembly 2023" is enabled
Resolution Note (fix version 2022.3.10f1):
Fixed a memory leak occurring when using TextCore.