Search Issue Tracker
By Design
Under Consideration for 2022.3.X, 6000.0.X, 6000.3.X, 6000.5.X
In Progress in 6000.4.X
By Design in 6000.5.X
Votes
1
Found in
2022.3.66f1
6000.0.57f1
6000.2.4f1
6000.3.0b1
6000.4.0a1
6000.5.0a1
Issue ID
UUM-117280
Regression
No
Crash on UNITY_FT_Stream_ReadAt when changing TMPro properties after unloading an AssetBundle
How to reproduce:
1. Open the attached “CrashRepro“ project
2. Open the “Assets/Scenes/SampleScene.unity“ Scene
3. Enter Play Mode
4. Repeatedly press the “Case 2“ button in the Game view
Reproducible with: 2022.3.66f1, 6000.0.57f1, 6000.2.4f1, 6000.3.0b1
Reproducible on: macOS 15.6.1 Sequoia (Intel), Windows 10 (by user)
Not reproducible on: No other environment tested
First few lines of the stack trace:
0x00007ff641e6d426 (Unity) UNITY_FT_Stream_ReadAt
0x00007ff641e71e6d (Unity) UNITY_tt_face_load_any
0x00007ff641e6ab83 (Unity) UNITY_FT_Load_Sfnt_Table
0x00007ff641ea5767 (Unity) otv_validate
0x00007ff641e70e0b (Unity) UNITY_FT_OpenType_Validate
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.
After reviewing the behavior, we've confirmed it aligns with the current design and intended use of the feature. We understand this may differ from your expectations or workflow.
We will close this case as 'As Designed.' If you have feedback on how the feature could better meet your needs, please let us know - we value your input and consider it in future improvements.
Resolution Note (6000.5.X):
Thank you for reporting a bug to Unity.
After reviewing the behavior, we've confirmed it aligns with the current design and intended use of the feature. We understand this may differ from your expectations or workflow.
We will close this case as 'As Designed.' If you have feedback on how the feature could better meet your needs, please let us know - we value your input and consider it in future improvements.