Search Issue Tracker
Active
Under Consideration for 2021.3.X, 2022.3.X, 6000.0.X, 6000.2.X, 6000.3.X, 6000.4.X
Votes
3
Found in
2021.3.39f1
2022.3.34f1
6000.0.7f1
6000.1.0a7
6000.2.0a1
6000.3.0a1
6000.4.0a1
7000.0.0a1
Issue ID
UUM-74015
Regression
No
TextMeshPro memory is not de-allocated when unloading scenes using Addressables.UnloadSceneAsync in Player
How to reproduce:
1. Open the attached “IN-78366” project
2. Build and run the Player (File → Build And Run)
3. Open the Memory Profiler window (Window → Analysis → Memory Profiler), and ensure the Player is targeted in the “Target Selection” dropdown menu
4. Press the “Capture” button
5. In the captured snapshot, navigate to the “Unity Objects” tab and enter “Font“ into the search bar
6. Take note of the search results
7. In the Player, press the Spacebar twice to load, and then unload a scene containing a TextMeshPro element
8. Repeat steps 4 to 6
Expected result: The TextMeshPro memory is de-allocated and the number of search results is unchanged
Actual result: The TextMeshPro memory is not de-allocated and additional search results are shown
Reproducible in: 2021.3.39f1, 2023.3.34f1, 6000.0.7f1
Reproducible on: Windows 11
Not reproducible on: No other environments tested
Notes:
- Using ClearFontAssetGlyphCache prevents a memory leak, but does not clear the first allocation
- in 2021.3.39f1 (Memory Profiler 0.7.1-pre.1) it is not possible to search as explained in the reproduction steps. However, it is possible to find the additional entries by using the “Compare Snapshots” feature
Comments (1)
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
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- Crash with “Fatal Error! The file ‘MemoryStream’ is corrupted!” when adding a large number in Font Character Rects Size field
nikita1995f
May 02, 2025 14:44
Same problem.
Any solution?