Search Issue Tracker
Fixed in 2022.2.X
Fixed in 2020.3.X, 2021.2.X, 2022.1.X
Votes
0
Found in
2019.4
2020.3
2021.2
2022.1
2022.2
Issue ID
1394062
Regression
No
[Particles] "ParticleSystem.GetTrails()" API forces "GC.Alloc" calls
Reproduction steps:
1. Open the attached "ParticlesTrailSample" project
2. Open the "SampleScene" Scene
3. Open the Profiler window (Window > Analysis > Profiler)
4. Enable "Deep Profile"
5. Enter Play mode
6. Observe the recorded frame calls in the Profiler Hierarchy
Expected result: "ParticleSystem.GetTrails()" doesn't force "CG.Alloc" calls
Actual result: "ParticleSystem.GetTrails()" forces "GC.Alloc" calls
Reproducible with: 2019.4.34f1, 2020.3.26f1, 2021.2.8f1, 2022.1.0b4, 2022.2.0a2
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note (fix version 2022.2):
Fixed in 2022.2.0a3