Search Issue Tracker
Duplicate
Votes
0
Found in
2017.1.0f3
Issue ID
947224
Regression
Yes
Particle System Sub Emitter maximizes CPU usage up to 95%
Reproduction steps:
1. Download project "Particle Bug.zip" and open in Unity
2. Select object "Problem Particle System" in Hierarchy
3. Enter Play mode
4. Select PostLateUpdate.ParticleSystemEndUpdateAll in Profiler
5. Disable / Enable Sub Emitters of "Problem Particle System"
Expected: CPU usage to be about 2 to 10%
Actual: maximum CPU usage is about 95% (reason for percentage is "Sub Emitter Particle" property Size over Lifetime)
Reproduced on: 2017.1.0b1; 2017.1.1f1; 2017.2.0b10; 2017.3.0a7
Not reproduced on: 5.6.3p2; 2017.1.0a6
Regression introduced: 2017.1.0b1
Note: "Sub Emitter Particle" property Collision also increases CPU usage, but not to that extent
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
This is a duplicate of issue #930933