Search Issue Tracker
Duplicate
Votes
0
Found in
2017.1.2f1
Issue ID
958321
Regression
Yes
UpdateTpl<1> crashes when entering to Play mode
To reproduce:
1. Download attached project "ParticleSystemBug.zip" and open in Unity
2. Open "Main" scene
3. Enter Play mode
Expected Result: Unity Editor successfully enters to the Play mode
Actual Result: Unity Editor crashes
Notes:
- This issue appears on Unity Editor and Standalone Build
- Stack trace is shared on comments section
- The script called "Particles" runs the Emit function in Start. There are two ParticleSystems, called - "CollisionOff" and "CollisionActive". "CollisionOff" is the ParticleSystem currently plugged into the "Particles" script and will crash Unity. "CollisionActive" will not crash Unity.
Reproduced on Unity 2017.1.1p4, 2017.1.2p1, 2017.2.0f3, 2017.3.0b4 and 2018.1.0a1
Not reproduced on Unity 5.6.4f1 and 2017.1.1p3
Regression on Unity 2017.3.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
- NavMeshManager.LoadData takes a long time and causes performance spikes when enabling a NavMeshSurface with already instantiated NavMeshLinks
- Shadows created by real-time Spotlights are rendered at a very low resolution on terrain when HDRPAsset Lit Shader Mode is set to Forward or Both
- “STP” in Project window > Advanced Upscalers by Priority menu list is shown as available to add when it is already added to the list
- Rename fails with an error “Canceling DisplayDialog” when renaming a Mipmap Limit Group in Project Settings > Quality after adding a new group
- Obsolete API warning CS0618: 'HDAdditionalLightData.SetIntensity(float)' is thrown when installing “Output Event Helpers” Samples to the project
This is a duplicate of issue #957427