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
- Uninitialized variable warning appears in the Inspector of a custom shader when the variable is initialized
- "Failed creating toolbar element from ID..." error is thrown when resetting the Scene view Overlay layout while an Asset Transformer Toolbox overlay is active
- Entity ID for Font Assets is serialized twice which throws an error when using Debug Inspector
- Play Mode can be entered when disabling Adaptive Performance and pressing either the Play Mode button or the keyboard shortcut to enter Play Mode before recompilation leading to errors and warnings thrown
- Parent ListView element also becomes selected when inner ListView element is selected
JamesBoink
Aug 31, 2021 19:36
Happens in 2020.3.4f
bbxlegend
Aug 20, 2021 11:38
Still broken in 2021.03.16f
O1lec1
Mar 15, 2021 14:31
Still broken.
Fillmore
Jan 14, 2021 23:10
Still happens on 2020.2.1f1
Allocation of 80 bytes at 0x13eed34f0
TLS Allocator ALLOC_TEMP_THREAD, underlying allocator ALLOC_TEMP_THREAD has unfreed allocations, size 80
Internal: Stack allocator ALLOC_TEMP_THREAD has unfreed allocations, size 80
To Debug, enable the define: DEBUG_STACK_LEAK in StackAllocator.h. This will output the callstacks of the leaked allocations
unity_-czh6Add1XgRzg
Oct 13, 2020 10:12
Just got this bug after creating a new Unity 2019.4 project, importing the MRTK v2.4, deleting SampleScene and creating a blank empty new scene
unity_-czh6Add1XgRzg
Oct 13, 2020 10:12
Just got this bug after creating a new Unity 2019.4 project, importing the MRTK v2.4, deleting SampleScene and creating a blank empty new scene
dgoodman-icf
Aug 22, 2020 00:47
Still happens in 2020.1.2
Barritico
Jun 12, 2020 20:57
2019.4.0f1... same
AhmadMcreator
May 30, 2020 03:28
Been trying to solve this for a couple of days now using peoples "fixes" but none of them work! I'm on 2019.3.4f1
abbasjafari
May 07, 2020 17:51
2019.3.0f6