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
- Packman: The same asset data is displayed differently in "Import" and "Remove" popups
- Reference to a deleted GameObject becomes "None" instead of "Missing" when the GameObject is restored with undo after entering and exiting Play Mode
- Size value in Particle System Curve's tab is highlighted with selection across all tab header
- Particle System Curve's Presets window has no visual indication of what preset is selected
- Blur shader doesn't work when the "Scene Color" Node is attached to the UI "Output" Node
Resolution Note (fix version 2022.3.10f1):
Fixed a memory leak occurring when using TextCore.