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 (132)
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
- ScrollView clips content when under an ancestor that has a filter set
- "Retrieving array element that was out of bounds" error thrown when attempting to remove a column from a Multi-Column List View
- Multi-Column List View horizontal scroll resets to left most position when scrolling vertically
- Floating License is lost for concurrent jobs
- Warning "Failed to insert item" is logged when Assigning Project to Organization's Project in the Project Settings
5argon
Nov 27, 2017 18:34
I can reproduce this on 2017.3 b10 after applying ETC2 crunch compression. It prints this repeatedly on play mode while the texture is in view.
gimic9912
Nov 19, 2017 18:43
Problem in Unity 2017.2.0f3
allenk00
Nov 14, 2017 09:00
same problem in 2017.2.0f3
GilCat
Nov 11, 2017 13:15
Same problem in Unity 2017.3.0b9
RKSW
Nov 10, 2017 20:57
For me, this is more an irritant than anything else. It constantly produces output to the error window adding clutter to the info I need during development.
MilesRenatus
Nov 08, 2017 15:33
Still having this issue in 2017.3.0b8 on Windows 10. Computer specs in case it is relevant: Intel i5-6300HQ, Nvidia GTX 950M, 8GB DDR4 RAM.
maiko
Nov 08, 2017 11:43
This is still happening for me in 2017.3.0b8. I am developing in Android.
gldio
Nov 07, 2017 14:57
same problem in version 2017.2.0f3 in win10. only occures after ios build and the fix is to restart unity.
VOTRUBEC
Nov 06, 2017 01:01
This is also appearing in 2017.3.0b6.
It seems to occur MORE frequently when the build window is open. The project is set to iOS.
The error seems to be generated whenever the mouse passes into and out of a window/tab. Therefore, moving the mouse normally can fill the error log with these logs and errors. It seems to occur only after the first Build to iOS. After that, the error message are constant.
I have a dual monitor setup. It seems even worse when the build window is on the second monitor, but that may simply be due to the fact the mouse pointer is entering and exiting the Unity windows more often.
KillStone1997
Oct 27, 2017 18:36
Having the same issue (on Windows, after updated unity to 2017.2.0f3).