Search Issue Tracker
Fixed
Fixed in 2022.3.57f1
Votes
0
Found in
2022.3.55f1
Issue ID
UUM-91901
Regression
Yes
"TLS Allocator ALLOC_TEMP_TLS" errors are thrown when unsuccessfully importing an FBX file
How to reproduce:
1. Open a new project
2. Import the attached “test.fbx“ into the project
3. Observe the Console
Expected result: Only “ImportFBX Errors: Couldn't import file“ error is thrown
Actual result: Many TLS Allocator errors are thrown continuously
Reproducible with: 2022.2.0a14, 2022.3.55f1, 2023.1.0a26
Not reproducible with: 2021.3.47f1, 2022.2.0a13, 6000.0.33f1, 6000.1.0b1
Fixed in: 2023.2.0a1
Reproducible on: Windows 11
Not reproducible on: No other environment tested
Notes:
- Extract the project again after reproducing the issue
- Removing the asset or restarting the editor does not stop the errors
- Error: TLS Allocator ALLOC_TEMP_TLS, underlying allocator ALLOC_TEMP_MAIN has unfreed allocations, size 32
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
Add comment