Search Issue Tracker
Fixed in 5.5.1
Votes
0
Found in
5.5.0f3
Issue ID
856877
Regression
Yes
[Shuriken] Error in TLS Allocator ALLOC_TEMP_THREAD when simulating particle system
Repro steps:
1. Open repro-scene from attached project.
2. Select Particle System in Hierarchy for it to Simulate.
3. Observe console errors:
Notes:
- Can't check for regressions as 5.5 projects can't be opened in 5.4. Assuming it's an upgrade issue as 5.5 just came out, so marking as a regression.
- Resetting particle system does not fix the issue. Does not seem to be SubEmitter-related.
- Creating a new scene and a new particle system still shows the same issue.
- Deleting the Library and Project folder had no effect.
- Getting no errors when opening in 5.6.0a6
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
- Crash on ShaderLab::ShaderState::ApplyShaderState when entering Play Mode and calling ShaderWarmup.WarmupShaderFromCollection with a shader that has dynamic_branch
- Crash on operator delete[] when a serializable structure in the System namespace is serialized by a MonoBehaviour
- [macOS] forward and backward mouse buttons are recognized as middle mouse button
- NavMeshModifier.OnEnable/OnDisable gets progressively slower when called repeatedly
- "System.Net.CookieContainer" throws an "ArgumentException" error when using a non-UTF-8 machine locale and hostname
KushyKitty
Dec 26, 2021 17:04
THIS IS NOT FIXED, at least not in the current version (2021.2.4f1) on my machine (2020 Macbook Air). I know this machine is not ideal for graphics & such but i should still be able to use Unity without this memory leak bringing Unity to its knees every time i simulate a stream of particles.
WagDan
Apr 20, 2017 10:32
I get this in 5.6, with no particles.
axomind
Apr 06, 2017 06:34
I get this issue after upgrade from 5.5 to 5.6... Disable all particle system doesn't change a thing
Skyfly
Jan 17, 2017 09:35
Even after deleting the prefab from the scene I get frequent 'Allocation of 768 bytes at 05ec8700' in masses.
Skyfly
Jan 17, 2017 09:34
See the same on basic scenes with 5.5.0p3 (fireworks prefab from standard assets) Only editor restart helps. Floods the console.
maikkel
Jan 07, 2017 23:31
...or not, now in play mode with fireworks playing, i get a ton of "Assertion failed" errors:
Assertion failed on expression: 'particles.array_size() == count'
Assertion failed on expression: 'count == particles.array_size()'
Assertion failed on expression: 'count >= toIndex'
They keep repeating...
maikkel
Jan 07, 2017 23:26
Ok, seems fixed in 5.6.0b3
maikkel
Jan 07, 2017 22:50
Downloaded Patch release 5.5.0p3, where this should be fixed. The same thing still happens with the particle systems. Re-Imported the Standard Assets, didn't work...