Search Issue Tracker
Fixed in 2.1.0.preview-1
Votes
0
Found in [Package]
2.0.1
Issue ID
1249079
Regression
Yes
[TextMeshPro] Selectable object memory leak when TMP_Dropdown is disabled/destroyed
How to reproduce:
1. Open attached project "case_1249079-TMP_Dropdown_Leak.zip"
2. In the Project window, go to Assets > Scenes and double-click "TestScene"
3. Click Play and then open the Console window
Expected result: No Selectable object leaks are logged
Actual result: TMP_Dropdown is logged as a leaked Selectable
Reproducible with:
TMP 1.4.0.preview.2a - 1.4.1 (2019.3.15f1)
TMP 2.0.0 - 2.0.1 (2019.3.15f1)
Not reproducible with:
TMP 0.1.2-preview - 1.2.1 (2019.3.15f1)
TMP 1.5.0-preview.1 - 1.5.0.preview-13 (2019.3.15f1)
TMP 2.1.0-preview.1 - 2.1.0.preview-13 (2019.3.15f1)
TMP 3.0.0-preview.1 - 3.0.0.preview-13 (2020.1.0b10, 2020.2.0a12)
Couldn't test with: 2017.4.40f1 (project errors), 2018.4.23f1 (project errors), 2019.3.15f1 (TMP 1.2.2 - 1.4.0-preview.1b)(errors in console window)
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Rendering locks up when not looking at a transparent material on Meta Quest 2
- Volumetrics break when using a Custom Pass to create a Thickness Buffer for Alpha Clipping
- All tests are run instead of only the failed ones when the "Rerun Failed" button is pressed
- GameObject is not masked when the "Render PostProcessing Effects" pass executes with a resolved non-MSAA Color target and MSAA DepthStencil target
- [Android] Gfx.WaitForGfxCommandsFromMainThread high performance usage and inconsistency when built Player scene has Canvas GameObject on a specific Project
Add comment