Search Issue Tracker
Won't Fix
Votes
0
Found in
2022.3.28f1
6000.0.0f1
Issue ID
UUM-71321
Regression
Yes
TextMeshPro memory leak occurs when reloading the scene using Addressables
How to reproduce:
1. Open “memoryLeak“ project
2. Navigate to File → Build and Run
3. In Player press space (keyboard)
4. Navigate to Window → Analysis → Memory Profiler
5. In the Memory Profiler window press “Capture New Snapshot“
6. Select the Player window
7. Press space twice
8. Repeat step 3
9. Observe the Total Memory of the Snapshots in the Memory Profiler
Expected result: No significant difference in memory
Actual result: More memory is allocated in the second Screenshot
Reproducible with: 2022.3.28f1 (3.0.8), 6000.0.0f1 (uGUI 2.0.0)
Not reproducible with: 2022.3.28f1 (3.2.0-pre.1)
Could not test with: 2021.3.38f1 (full memory is not captured)
Reproducible on: Windows 10, Windows 11
Not reproducible on: No other environment tested
Notes:
- Make sure that the Memory Profiles is connected to the Player
- Regression happened at the TextMeshPro package version 3.2.0-pre.1 (refer to internal notes)
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
- [Android][OpenGL]Soft Shadows contain artifacts when the OpenGL Graphics API is used
- The particle system prewarm flag is ignored when calling the Start function after the Stop function
- The Scene view flickers when moving around if there are visible Hair Shaders
- The gradient ShaderGraph is inverted when using the Perceptual blend mode
- Particle System allocates large amounts of memory when it is very far away from the origin of the Scene
Resolution Note:
The user can work around this. We however took note that this process should be better documented and that we could perhaps handle this better (behind the scene) instead of requiring the user to call unknown API functions.
See the comment for the workaround