Search Issue Tracker
Fixed in 6000.3.15f1
Fixed in 6000.6.0a4
Votes
3
Found in
6000.0.73f1
6000.3.13f1
6000.4.2f1
6000.5.0b3
6000.6.0a2
Issue ID
UUM-139918
Regression
No
Font Engine Layout Tables memory increases when repeatedly entering Play Mode with custom fonts used in a UIDocument
Reproduction steps:
1. Open the attached “BugFontTables.zip” project
2. Open the “Assets/Scenes/SampleScene.unity” scene
3. Open Window > Analysis > Memory Profiler
4. Press “Capture New Snapshot” (to capture a baseline snapshot)
5. Use an autoclicker or manually repeatedly click the Play button to enter and exit Play Mode for at least 5 minutes
6. In Memory Profiler, press “Capture New Snapshot”
7. Compare the snapshots in “All Of Memory” and inspect: Native > Unity Subsystems > Font Engine > Layout Tables
8. Observe Memory usage increase in later Snapshot
Actual result: Layout Tables memory allocation grows from ~0.43 GB to ~0.62 GB
Expected result: Memory allocation remains about the same
Reproducible with: 2023.1.0a1, 6000.0.73f1, 6000.3.13f1, 6000.4.3f1, 6000.5.0b5, 6000.6.0a2
Reproducible environment: Windows 11
Not reproducible environment: No other environments tested
-------------
Related slack thread: https://unity.slack.com/archives/C5AURAWV7/p1776345973505719?thread_ts=1776345954.213669&cid=C5AURAWV7
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
- Some post-processing volume overrides only update after a refresh when using HDRP
- Video Player glitches when Skip On Drop is enabled
- GameObject movement in Scene view becomes stuttery and intermittently freezes when using non-standard pointers across editor tabs or window boundaries
- Addressables.CheckForCatalogUpdates() always returns 0 when "Only update catalogs manually" is enabled
- VFX Graph forces a lengthy recompilation freeze when exiting Play Mode with a cloned Render Pipeline asset
Resolution Note (fix version 6000.3.15f1):
Fixed in 6000.6.0a4
Resolution Note (fix version 6000.6.0a4):
Fixed in 6000.6.0a4