Search Issue Tracker
Fixed in 2017.1.X
Votes
0
Found in
2017.1.0b1
Issue ID
900183
Regression
Yes
Assertion "ALLOC_TEMP_THREAD..." appears, when closing Unity in playmode with unsaved scene
Reproduction steps:
1. Create new project.
2. Change Camera position Y to 21 (or any other change). DO NOT SAVE
3. Press Play.
4. Try to close Unity.
5. Warning "Scene have been modified" appears. Press Save.
6. Window "Save scene" appears. Close it.
Expected result: Nothing will change, play mode stops.
Actual result: Play mode stops, output in console:
Message: "Allocation of 48 bytes at 0608a060"
Error: "Assertion failed: TLS Allocator ALLOC_TEMP_THREAD, underlying allocator ALLOC_TEMP_THREAD has unfreed allocations"
Note: Prior to 5.6, the number of bytes is 40. Location "at..." is different in each version.
Reproduced on: 5.3, 5.4, 5.5, 5.6, 2017.1.0b1.
Works fine on: 5.1.0f3, 5.2.5f1.
Regression introduced in: 5.3.
Comments (28)
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
- [VFX Graph] ArcCone Direction computation is wrong in Base Mode
- [Android] [Galaxy Tab] A singular Pen touch logs a Pen touch event and a singular finger touch event when logged using "VisualElement.RegisterCallback" with "Pointer(Up/Down)Event"
- Crash on D3D12DescriptorCache::Deallocate or vkGetInstanceProcAddr when loading RenderDoc in a specific Scene
- [HDRP] Lit material preview is rendered incorrectly with a mask map
- The "LerpWhiteTo" missing function displays an error when the Shadows.hlsl shader is included in a Shader file
DJ_JW
Nov 22, 2017 19:59
Also same error after building for IOS.
Unity 2017.2.0.p2:
Assertion failed: TLS Allocator ALLOC_TEMP_THREAD, underlying allocator ALLOC_TEMP_THREAD has unfreed allocations
2017.1.1f1
Nandos_ZA
Nov 18, 2017 10:28
Same problem here when building for iOS.
Kougasama
Nov 05, 2017 22:03
Same here. Error started appearing all of a sudden and doesn't stop anymore. Usually happens when any scene other than the initial one is loaded. Compiled project even crashes at times when loading new scene.
Grafos
Oct 30, 2017 05:06
Not fixed, using 2017.1.1f1
bhermer
Oct 23, 2017 17:55
Happens to me after compiling for IOS on win10 2017.1.2.f1 I can play, but it just rolls that error in, making debugging the console impossible
Mazoin
Oct 18, 2017 14:13
This is still not 'fixed' at all even in 2017.2.0f3
Mazoin
Oct 17, 2017 12:05
Allocation of 34 bytes at 05bed0e0
Assertion failed: TLS Allocator ALLOC_TEMP_THREAD, underlying allocator ALLOC_TEMP_THREAD has unfreed allocations
thousands of logs in seconds
RKSW
Oct 12, 2017 23:51
Assertion failed: TLS Allocator ALLOC_TEMP_THREAD, underlying allocator ALLOC_TEMP_THREAD has unfreed allocations
Received error on build for iOS on Windows box. The output does build in XCode on Mac, so not at all sure what's going on ere.
I first encountered the error running 2017,2 Beta versions.
uzumaki258
Oct 03, 2017 01:35
Assertion failed: TLS Allocator ALLOC_TEMP_THREAD, underlying allocator ALLOC_TEMP_THREAD has unfreed allocations
2017.1.1f1
jestergames
Sep 25, 2017 23:34
Same here, cant publish to iOS anymore!!! Using 2017.2.0f1