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
-
JOSHUA524
Aug 20, 2020 12:22
If VR support used to enable play mode this might help to set data. When you exit the play mode editor crashes in actual result and not give the expected result. The https://www.bestcustomessay.org/case-study/ enlightens some points to resolve this tracker issue. You can check this for more info.
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
- Inspector's custom tooltip is displayed incorrectly when the name is truncated in UI toolkit
- Crash on ScriptableRenderLoopDraw when rendering a specific VFX in Play Mode
- The script is not renamed in the Project window when renaming and a compilation Error is present
- Average FPS in Play Mode degradation on a newly created BiRP project when it's upgraded from 2020.3.48f1 to a newer Editor version
- DecoratorDrawer indentation is incorrect when it is called with EditorGUI
This is a duplicate of issue #1163721