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
indydevstudio
Nov 19, 2018 03:35
unity 2018.2.15f1 this same!
radiantboy
Apr 07, 2018 04:03
Just started getting this in 2018.1.0b13!
Seraphic572
Feb 28, 2018 09:37
Need Help with this issue in unity 2017.2.0f3 ...
XCO
Feb 18, 2018 03:39
Need help with this UNITY 2017.03
darknik89
Feb 11, 2018 14:20
BILGISOFT, thx bro!
Bilgisoft
Feb 09, 2018 07:06
I solved this error. You must change .net option in user preference .net 3.5 to .net 4.6.
mild7lss
Feb 01, 2018 02:44
It is troubled gameobject make to prefab. then export package.
and another project import this package.
use prefab, then disappear error.
But I don't know reason.
I use 2017.3.0f3/windows 10.
Zeeppo
Jan 24, 2018 15:55
It's not resolved! Still getting this error on 2017.3.0f3
xiaotianchen
Jan 15, 2018 05:36
Not fixed, getting on 2017.3.0f3. Please rise the priority.
q635239856
Jan 10, 2018 07:35
Not fixed ,Getting it on 5.6.3