Search Issue Tracker
Won't Fix
Won't Fix in 6000.6.X
Votes
0
Found in
6000.0.68f1
6000.3.10f1
6000.4.0b10
6000.5.0a7
6000.6.0a1
Issue ID
UUM-134939
Regression
No
TextMeshPro - Text Component with empty string makes Mesh Collider throw.
Reproduction steps:
1. Create a new project
2. Select any GameObject, click “Add Component” button and select TextMeshPro - Text Component (Mesh > TextMeshPro - Text)
3. Click “Add Component” button again and select Mesh Collider Component (Physics > Mesh Collider)
4. Observe the Console
Actual result: “[Physics.PhysX] cleaning the mesh failed UnityEditor.EditorApplication:Internal_CallDelayFunctions ()” error is thrown
Expected result: No errors or warnings are thrown
Reproducible with: 6000.0.68f1, 6000.3.10f1, 6000.4.0b10, 6000.5.0a7
Reproduced on: Windows 11, macOS Sequoia 26.2 (M4)
Note: Issue is not reproducible when Mesh Collider Component is added before TextMeshPro - Text Component
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note:
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.
Resolution Note (6000.6.X):
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.