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
Comments (67)
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
- PlayerPrefs get corrupted when a minimized fullscreen Player is closed through the Taskbar
- "To Debug, run app with -diag-job-temp-memory-leak-validation cmd line argument. This will output the callstacks of the leaked allocations." warning is printed when JobTempMemoryLeakValidation switch is enabled
- Main Thread stalling when loading Audio Source asset asynchronously while preloading another Audio Source asset
- Material artifacts occur in the Material Preview window when baked lighting is applied to scenes
- “ArgumentOutOfRangeException” after saving, reseting and re-add Default Tile Palette Tools to the list in Preferences window
Yue
Jan 10, 2018 01:15
How to re-submit the issue? The problem didn't resolved at 3.0p1
SeRasul
Jan 09, 2018 20:32
Editor version also 2017.3.
SeRasul
Jan 09, 2018 20:32
Guys, I also getting the error and it fully stuck my work. Please, fix it.
clckwrk
Jan 08, 2018 21:17
Still getting this error in 2017.3.0p1
mogwhy
Dec 13, 2017 13:01
5.5.5p2 editor error
TLS Allocator ALLOC_TEMP_THREAD, underlying allocator ALLOC_TEMP_THREAD has unfreed allocations
elamda
Dec 03, 2017 14:55
Not fixed ,Getting it on 5.6.2f1
arikm
Nov 29, 2017 04:00
no particles..
compiling in win10/unity 5.6.4 for iOS, and build stops with this error.
J5Dev
Nov 19, 2017 12:51
Unity 2017.2.0f3 and still this problem is there...
uzumaki258
Oct 14, 2017 07:29
Not fixed , Still error in Unity 2017.1 0f3 .
brian_mcgee_nb
Oct 11, 2017 16:24
also, I tried in an empty scene - and the problem persists