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
- Unity Events added to a ScriptableObject are not invoked if they are added in Edit mode and their Call State is set to "Runtime Only"
- The Visual Effect GPU Event is forced into sleep until another Event is sent when the visual effect consists of two particle systems that communicate with Trigger Event set to On Die
- Nativeplugin Vulkan image gets deleted while in use and AccessTexture returns an invalid texture causing a crash or corruption when QualitySettings.anisotropicFiltering is called
- Error "DllNotFoundException: __Internal assembly:<unknown assembly> type:<unknown type> member:(null)" when attaching a managed debugger for the build of a specific project with Mono Scripting Backend
- Unable to select UI Toolkit Foldout element when using a gamepad controller
This is a duplicate of issue #930933