Search Issue Tracker
Won't Fix
Votes
1
Found in
2018.4
2019.2
2019.3
2019.3.0f3
2020.1
Issue ID
1206509
Regression
No
Editor crashes when calling ComputeShader.Dispatch() with too many threads
How to reproduce:
1. Open the attached project named "Case_1206509"
2. Open the Gameplay Scene located in the Scenes folder
3. Enter Play mode
Expected behavior: Editor functions properly or throws an error due to a high number of threads used
Actual behavior: Editor crashes
Reproducible with: 2018.4.15f1, 2019.2.18f1, 2019.3.0f5, 2020.1.0a19
Could not test with: 2017.4.36f1(Scripts breaking after downgrading)
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
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Resolution Note:
There is no way to a priori know that the amount of work in a compute shader dispatch is too much for the GPU causing a driver timeout. In the future if we get device lost recovery and improved debug info from driver we might have more informative error.