Search Issue Tracker
Fixed in 2018.1.X
Fixed in 5.6.X, 2017.1.X, 2017.2.X, 2017.3.X, 2017.4.X
Votes
147
Found in
2017.1.0b8
Issue ID
921915
Regression
Yes
"Assertion failed: TLS Allocator ALLOC_TEMP_THREAD..." error is shown after building the project for iOS'
To reproduce:
1. Create a new project
2. Build it for iOS
3. Observe the console after the build has finished
Expected: no assertion errors are shown after building the project for iOS
Reproduced in 5.6.0a2, 5.6.1p4, 2017.1.0b8, 2017.2.0a4
Did not reproduced in 5.5.4f1, 5.6.0a1
Regression introduced in 5.6.0a2
Not reproducible in 2017.3.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
- Symbolic links disappear when a .xcframework file is added through the Unity Editor
- Errors regarding importing occur upon opening a project when the "Library" folder is deleted
- MeshRenderer.sortingLayerID cannot be changed when change is being done in a built Player
- Warnings related to App Icon are being thrown when building project to VisionOS Platform
- [Mobile] Developer Console does not appear when an error is thrown
Thenumberfly
Feb 01, 2018 03:12
I've had this error in multiple projects from 5.6 through 2017.3
huang-sir
Jan 30, 2018 12:13
same problem in 5.6.3
njansson
Jan 28, 2018 10:24
Unity 2017.3.0f3
Assertion failed: TLS Allocator ALLOC_TEMP_THREAD, underlying allocator ALLOC_TEMP_THREAD has unfreed allocations, size 69
Would really appriciate a fix as I can no longer build for IOS.
tarahugger
Jan 26, 2018 17:50
Error in fresh install of 2017.3.0f3 building to IOS using Unity's official build tutorial and assets.
https://unity3d.com/learn/tutorials/topics/mobile-touch/building-your-unity-game-ios-device-testing
Assertion failed: TLS Allocator ALLOC_TEMP_THREAD, underlying allocator ALLOC_TEMP_THREAD has unfreed allocations, size 132
Zeeppo
Jan 26, 2018 15:43
It works for a while...
danvlad
Jan 26, 2018 13:34
Rename "Library" from project folder. It works...
Zeeppo
Jan 25, 2018 17:06
I've deleted the folder Library, obj and UnityPackageManager, started Unity again, all the things were imported again (hours of work lost) and then the error was gone. But just for a few hours. Now it's happening again. As I can see on Google, this error is old, really old. The guys from Unity say they fixed it over and over again in every thread (there's a lot), but the truth is it was never fixed and maybe they just don't know what causes it and how to fix it.
Zeeppo
Jan 25, 2018 17:02
No, I think it doesn't affect the build. But it is extremely annoying coz it's impossible to debug in play mode
eookog
Jan 25, 2018 09:02
In my case, I updated Unity from 5.6 to 2017.3.0p3
It was fine when platform was pc,mac but as soon as I converted to android, got this error.
Assertion failed: TLS Allocator 'ALLOC_TEMP_THREAD, underlying allocator ALLOC_TEMP_THREAD has unfreed allocations, size 11184864'
Also, in play mode, I got this error !
Is there any temporary solution??
And... is it critical for Android, iOS App (release version) ??
Zeeppo
Jan 24, 2018 15:57
Is getting this error: Assertion failed: TLS Allocator ALLOC_TEMP_THREAD, underlying allocator ALLOC_TEMP_THREAD has unfreed allocations, size 349552
Unity 2017.3.0f3 Windows 10 Android platform