Search Issue Tracker
Duplicate
Votes
0
Found in
2018.4.0f1
2019.1.0a1
2019.1.2f1
2019.2.0a1
2019.3.0a1
Issue ID
1161050
Regression
No
[XR] Editor crashes with ComputeBuffer::SetData when exiting the Play Mode if there's a specific Particle System in the scene
How to reproduce:
1. Open the user's project
2. Enter the Play Mode
3. Exit the Play Mode
Expected result: Editor does not crash
Actual result: Editor crashes
Reproducible with 2018.4.2f1, 2019.1.7f1, 2019.2.0b6, 2019.3.0a6
Note1: Crash is reproducible only when "Particle System_Algies" or "Particle System_Bubbles (1)" Game Objects are enabled together with the "Player" Game Object
Note2: Could not test with 2017.4 due to compiler errors
Last 5 Lines of Stack Trace:
0x00007FF694812460 (Unity) ComputeBuffer::SetData
0x00007FF6933216BF (Unity) GeometryJobTasks::PutGeometryJobFence
0x00007FF69331E102 (Unity) GfxDevice::EndGeometryJobFrame
0x00007FF693D97C2E (Unity) GfxDeviceWorker::RunCommand
0x00007FF693DA282B (Unity) GfxDeviceWorker::RunExt
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
- VFX Graph particles are not culled when using URP and Frustum Culling is enabled on VFX Mesh Output
- 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
This is a duplicate of issue #1163721