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
- Sprites is not rendered in a SRP Batcher when Sprite Mask is removed after it was previously set
- Crash on MemoryProfiler::GetAllocationRoot when entering Play mode on a specific project
- Video Player preview is not shown when Inspector preview is converted to Floating Window
- Invalid signature package console message is not visible after package import when Console has 'Clear on Recompile' setting enabled
- Cannot interact with GameObjects in the Hierarchy window by using shortcuts or edit menu when selecting a GameObject in the Hierarchy with a “Select” window opened
EthanHooper1023
Mar 29, 2022 18:53
this error spams the console in 2020.3.32
it also happens when I push to unity collaborate in 2020.3.25
pjblenkarn
Mar 23, 2022 02:22
Still happening in 2020.3.30, specifically around publishing changes to Collaborate
EduardoBlacksmith
Mar 15, 2022 14:07
still broken in 2020.3.27f1
Blacklabel_
Jan 03, 2022 10:31
I started getting this issue after publishing with unity collab. Closing and reopening seems to have resolved it.
piers_audiomob
Dec 14, 2021 14:11
In my case, bug occurred directly after upgrade, no build required, and the setting was for Standalone/PC.
A restart sorted it, and the bug has not recurred after building for iPhone.
piers_audiomob
Dec 14, 2021 13:50
Reproduced when upgrading from 2018.4.36f1 to 2020.3.12f1.
Please re-open.
vincurekf
Nov 26, 2021 19:03
Still happens in 2021.2.3f1
Nerzal
Nov 13, 2021 15:25
Still happens in 2022.1.0a13
cgrow67
Sep 16, 2021 15:18
I'm recently seeing this in 2021.1.21f1.
ScourgeGames
Sep 06, 2021 00:17
Still broken 2019.3.4f1.
But thanks for closing the voting on a "fixed" bug. Haha