Search Issue Tracker
Fixed in 5.5.2
Votes
4
Found in
5.5.0p3
Issue ID
864122
Regression
Yes
TLS ALLOCATOR ALLOC_TEMP_THREAD error caused by particle systems
Steps to reproduce:
1. Download and open the attached project
2. Drag the Fireworks prefab into the scene
3. Observe the console
Expected result: no errors
Actual result: ERROR IN TLS ALLOCATOR ALLOC_TEMP_THREAD
Reproduced on: 5.5.0p3
Not reproduced on: 5.4.4f1, 5.6.0b3
Notes:
-in this case, caused by the Fireworks prefab from standard assets
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
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
brian_mcgee_nb
Oct 11, 2017 16:24
Issue not resolved.
Unity 5.6.2. No particles in use. None existing in the standard assets folder.
Working on android no problems. But switching to iOS even when not running the game I get:
Allocation of 34 bytes at 061710e0 // I get a LOT of these
TLS Allocator ALLOC_TEMP_THREAD, underlying allocator ALLOC_TEMP_THREAD has unfreed allocations
When just in editor mode, these message pop up every minute or so. When I do a test run, they flood my console.
cheesepant
Oct 06, 2017 22:39
I also getting this error in 2017.1.0f3. This has not been fixed. Does unity not care?
Dev_Ankit
Oct 04, 2017 02:54
It's still NOT FIXED
One-Zero
Sep 30, 2017 03:08
yesterday I got this error. I am using Unity 2017.1.1f1
cheesepant
Sep 29, 2017 21:53
Not fixed. Getting it on 2017.1.1f1 All I have is ar kit asset and free zombie asset.
htmoore
Sep 23, 2017 08:41
Not fixed. After switching from Android to iPhone I started getting this error. Version 2017.1.1f1
IgorAherne
Sep 20, 2017 05:57
encountered in 2017.1.0f3 after building to iPhone 5
IgorAherne
Sep 20, 2017 05:56
Not fixed
2rusbekov
Sep 18, 2017 09:31
2017.1 After switching platform console full of these errors.
Muhand
Sep 08, 2017 03:22
This issue is not resolved. I am on 5.6.0 and still same. Not sure how is it marked solved. By the way, this doesn't only happen in the Fireworks prefab.