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
- “[Worker0] Could not generate preview image“ error when opening macOS native plugin in the Inspector with Architecture to build for set to ARM 64-bit
- [iOS] Application.absoluteURL is empty on Awake/Start when opening via deep link with Splash Screen disabled
- Crash on MemoryManager::Deallocate when rapidly calling Addressables.LoadAssetAsync
- Crash on physx::shdfnd::atomicIncrement when adjusting values on a character controller component after entering Play mode in Prefab edit mode
- [Rendering Debugger] [NewInputSystem] Debug Overlays in Play mode throws InvalidOperationException when using New Input System
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