Search Issue Tracker
Fixed
Fixed in 2021.3.45f1, 2022.3.48f1, 6000.0.18f1, 7000.0.0a1
Votes
0
Found in
2023.1.0a24
2023.2.0a1
2023.3.0a1
6000.0.0b11
7000.0.0a1
Issue ID
UUM-20120
Regression
No
[Profiler] Mesh memory remains accounted after disposal when using Mesh API
Reproduction steps:
1. Open the "MeshMemoryRepro" project
2. Open the SampleScene
3. Open the Profiler and enter Play Mode
4. Select a frame now and after a minute each time observing mesh memory and total used memory (more specifically the graphics memory)
Expected result: Mesh memory does not significantly increase and it cannot get higher than graphics memory or total used memory
Actual result: Mesh memory keeps increasing and does not correlate with graphics memory or total used memory
Reproducible versions: 2020.3.41f1, 2021.3.12f1, 2022.1.20f1, 2022.2.0b12, 2023.1.0a15
Reproducible OS: macOS Monterey 12.0.1 (Intel), Windows 11
Notes:
1. Also reproduced when profiling a Player
2. Looks like a misinformation issue in the Profiler as the increased memory does not seem to crash low-memory mobile devices
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Test Runner’s vertical scrollbar overlaps with the up and down arrows and upper toolbar tabs when the window is minimized
- The Input Field view is not updated when deleting lines of text
- The scrollbar does not respect empty lines in the Input Field
- “Texture Atlas Viewer“ button text overlaps another button when the UI Toolkit Debugger is narrowed
- Thresholds are no longer automatically calculated after deleting Motion fields in Blendtrees
Add comment