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
Comments (131)
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
- GenericDropdownMenu does not disappear when a dropdown selection that is shown with PopupWindow.Show() is pressed
- Environment is partially black when re-opening the newly created HDRP project for the second time
- Manual Reference button for Render Graph section in Rendering Debugger opens a missing Manual page
- Water Surface is missing the Wireframe when Scene is switched to Shaded Wireframe mode
- Water surface is not rendered when using Unlit Draw Scene view mode
fourthWallArtist
Mar 30, 2018 16:50
If you have a big project do not delete Library folder it will revert the platform. It will take long time to load unity and switch back to the platform you had set. If you have lots of textures you will have to wait a long time.
michielMV
Mar 29, 2018 13:08
Fixed this issue on 2017.3.0f3. Toggled off Crunch Compression on all images, then deleted Library and UnityPackageManager. When I switched platform to Android again, the error was gone.
armleghead
Mar 06, 2018 14:14
I got this error after switching my project to android and building a apk, unity 2017.3.0f3
Egil-Sandfeld
Mar 05, 2018 12:23
**Update**
Dang, that is, it actually stopped the error as I was running the Windows platform in build settings. Once I switched back to Android, the issue came back.
Egil-Sandfeld
Mar 05, 2018 12:15
I fixed this issue by deleting the following folders in my project:
/Library
/Temp
/UnityPackageManager
I restarted, and the error did not spawn any longer.
Before this, I tried Bilgisoft's solution which did not help.
info_unity94
Feb 28, 2018 10:58
Does anybody solved this issue?
I did not find any solution for the building problem for iOS in Unity also by installing the most recent patches released by Unity team
Thanks to everybody
DAVcoHL
Feb 22, 2018 10:52
In 2017.3.1f1 I am seeing this error when setting "PlayerSettings.iOS.iOSManualProvisioningProfileID".
Repro'd on both Win10 and Win7.
Everything seems to continue to work fine but, once this has occurred, editor updates will cause the messages to spam the console, requiring a Unity restart to clear.
MaskedMouse
Feb 21, 2018 11:28
In my previous comment what I meant with "they don't clear their native arrays in the process" I meant Unity
MaskedMouse
Feb 21, 2018 11:27
It happens on Unity 2017.3.1p1
fresh project -> build for iOS -> TLS allocator error afterwards.
It is incredibly annoying if you want to build and then debug some things in the editor because the log is getting spammed. So even if it is a "minor / comestic" issue, it is interfering with debugging.
Slowing down debugging after a build for iOS.
For those who said removing crunch compression works. Thats a seperate TLS allocator issue.
They probably don't clear their native arrays properly somewhere in the process.
I did not have this issue for Android builds when using crunch compression for ETC2.
CrazyPhysics
Feb 19, 2018 14:22
Same.. please fix :)