Search Issue Tracker
Fixed
Fixed in 2022.3.X, 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
- Play Mode Scenario selection/highlight is too long and out of its bounds when the Play Mode Scenario window is opened after maximizing
- Duplicated groups and incorrect grouping in UI Builder when using UxmlElementAttribute: libraryPath
- Asset name is not shown in the Undo History window when a sprite is modified
- Moving a Tab to a floating window fails when floating windows are docked next to each other
- Crash on UNITY_FT_Render_Glyph_Internal when Generating Font Atlas in the Font Asset Creator Window
Resolution Note (fix version 2022.3):
Fixed a memory leak occurring when using TextCore.