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
- Documentation page is not displayed when the "VFX Value Noise 3D" question mark is clicked
- Texture Mipmap Streaming uses wrong scales after Materials are changed at runtime
- Texture Mipmap Streaming doesn't work with HDRP/Lit shader's UV tiling
- Object overlay camera does not render when Depth/Stencil Buffer is disabled
- Shadows are not rendered on the transparent material when the "Deferred" Rendering Path is selected
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.
Tx
Dec 28, 2017 14:51
Same issue for me. Unity 2017.3.0f3.
Can't work anymore, last version hadn't any issue. Now all blew up.
Thanks unity. :-(
rattlesnake
Dec 22, 2017 09:18
Yes in fact, as soon as you add crunch compression, you get the error.
Thank you unity for telling us to use your great new crunch compression version :
https://blogs.unity3d.com/2017/12/19/unity-2017-3-is-here/
m0guz
Dec 22, 2017 04:14
@RATTLESNAKE 's answer solved my problem.