Search Issue Tracker
Fixed in 3.0.4
Fixed in 1.5.4, 2.1.4
Votes
1
Found in [Package]
3.0.3
Issue ID
1305311
Regression
No
TextMeshPro keeps resizing memory buffers when setting text with length difference more than 100
How to reproduce:
1. Open the user's attached project ("TextMeshProGC.zip")
2. Load "SampleScene"
3. Open the Profiler and start recording
4. Enter Play mode
Expected results: GC allocations subside over time (memory is reused)
Actual results: GC allocations continue indefinitely, memory is not reused
Reproducible with: TMP 1.5.0, 1.5.3 (2018.4.31f1), TMP: 2.1.0, 2.1.3 (2019.4.19f1), TMP 3.0.0, 3.0.3 (2020.2.3f1, 2021.1.0b5, 2021.2.0a3)
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
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Resolution Note (fix version 3.0.4):
Fixed in TMP 3.0.4 which is available on Unity 2020.1.0a11 and above
TMP Components created with an older version of TMP have to have vertexBufferAutoSizeReduction set to false manually
Resolution Note (fix version 2.1.4):
Fixed in TMP 2.1.4 which is available in Unity 2019.1.0a1 and above
TMP Components created with an older version of TMP have to have vertexBufferAutoSizeReduction set to false manually
Resolution Note (fix version 1.5.4):
Fixed in TMP 1.5.4 which is available in Unity 2018.4