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
- Inspector's custom tooltip is displayed incorrectly when the name is truncated in UI toolkit
- Crash on ScriptableRenderLoopDraw when rendering a specific VFX in Play Mode
- The script is not renamed in the Project window when renaming and a compilation Error is present
- Average FPS in Play Mode degradation on a newly created BiRP project when it's upgraded from 2020.3.48f1 to a newer Editor version
- DecoratorDrawer indentation is incorrect when it is called with EditorGUI
Todd-Wahoske
Jan 10, 2018 20:44
Repro in Unity 2017.3.0f3 with (Build Settings) platform set to Android. Did not occur when platform was set to PC/Mac & Linux Standalone.
*Note this happened *right* after submitting Crunch textures for the project on PC/Android/iOS.
My estimated guesses:
* crunching small textures is bad? (<32x32 to 128x128)
* crunching certain types of textures is bad (UI, particles, )
* crunching atlas packed (tagged) textures with different crunch settings is bad
* it's Trump's fault? ;) *cough*
Was super duper looking forward to Crunch results, so hoping this can get fixed for the next update. thx!
cain06
Jan 10, 2018 15:35
2017.3 just to clarify
cain06
Jan 10, 2018 15:34
I am also having this issue. Building for iOS but from a Windows PC, error shows up in the Console in Unity, but the build is successful anyways
valentinwinkelmann
Jan 08, 2018 18:33
Same here, unity 2017.3.
After building on Android i get this **** bug.
Making a new Clean project dosn't work.
MichalDev
Jan 08, 2018 12:34
For me also deleting everything except Assets, Project Settings and Soluction Files fixed the issue
Zaedoux
Jan 07, 2018 03:24
I had this same issue in version 2017.2.0f3 and solved it by deleting everything from my project folder (in the explorer) EXCEPT:
- Assets
- ProjectSettings
- Any Visual Studio Project/Solution Files
Ludomade
Jan 05, 2018 07:22
Happening here on 2017.3.0p1
Shame, really wanted to use the new crunch compression on Android.
warren-miller-maltd
Jan 01, 2018 09:32
same problem in 2017.2.0f3
RaventurnPatrick
Dec 31, 2017 17:38
Having this issue with 2017.3 (release) in the Editor when choosing the Android target. Also weird crashes on Android probably related to the new crunch compression features (not occuring with 2017.2 or before)
Zaegun
Dec 29, 2017 19:02
Unity 2017.3.0f3 is giving me this error when I build for iOS.
I made sure none of my textures are using Crunch compression as someone mentioned previously, but that doesn't appear to be working on my project. Clearing it does nothing as it'll pop up again and again until I restart the editor.