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
- Camera.current returns null when Camera.targetTexture is set to null in OnPostRender
- Crash on BaseHierarchyProperty::Next when opening a specific project
- Shader Compilation for projects with lots of Shaders can be slow (i.e. VFX Graph asset heavy projects)
- The Editor hangs when opening a project that uses local packages and Version Control
- Area Light is culled when Camera Frustrum is outside the lights range
facla2
Dec 16, 2017 03:25
Issue is occurring on Unity 2017.3.0f2 on my project.
It corrupted a few of my prefabs (it was reset to initial state; found in the source control diff).
No reason found so far.
ZzappSizzler
Dec 15, 2017 01:46
Using 2017.3.0f Apart from the error messages in the Console, everything else appears to be working fine.
ronaldrerosa
Dec 14, 2017 18:26
Found in Unity 2017.2.0f3.. sometimes when i get the error, unity stops responding to any mouse clicks so i have to force quit it and relaunch the whole application. Hope this gets fixed. Also I tend to reproduce the error more often when i hit save.
m0guz
Dec 10, 2017 13:10
Same problem in 2017.3.0f2
NakyYang
Dec 07, 2017 07:28
same problem in 2017.2.0f3
Kholeslaw
Dec 01, 2017 14:31
Windows 10 64
2017.2.0f3
Building iOS project results in the console being spammed with ALLOC_TEMP_THREAD errors.
This happens on an empty/clean project. Default settings.
The only fix is to restart Unity after every build.
FlorentFal
Nov 28, 2017 09:14
Appear on Unity 2017.3.0b10
Assertion failed: TLS Allocator ALLOC_TEMP_THREAD, underlying allocator ALLOC_TEMP_THREAD has unfreed allocations, size 69
0x00000001412F2D86 (Unity) StackWalker::GetCurrentCallstack
0x00000001412F38FF (Unity) StackWalker::ShowCallstack
0x00000001411B2B80 (Unity) GetStacktrace
0x00000001406D86C3 (Unity) DebugStringToFile
0x00000001406D8EA1 (Unity) DebugStringToFile
0x000000014038C304 (Unity) TLSAllocator<StackAllocator>::FrameMaintenance
0x000000014037B5F0 (Unity) MemoryManager::FrameMaintenance
0x000000014071E3F4 (Unity) `InitPlayerLoopCallbacks'::`33'::PostLateUpdateMemoryFrameMaintenanceRegistrator::Forward
0x000000014071B9D4 (Unity) PlayerLoop
Krustbox
Nov 28, 2017 00:00
Exact same thing here, with the added problem of my built IOS project being corrupted. When loaded onto device it loads and after the splash screen just shows a 2-tone gray screen, half and half, almost like what you see in editor part way through the build process. my game is completely useless at the moment.
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