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
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- The layout system is failing to correctly calculate or apply the height of the Japanese fallback font when the primary English font's metrics are used
Resolution Note (fix version 2022.2):
Fixed in 2022.2.0a3