Search Issue Tracker
Fixed in 2020.2.X
Fixed in 2019.3.X, 2020.1.X
Votes
0
Found in
2019.1.0a4
2020.1.0a21
2020.2
Issue ID
1221374
Regression
Yes
Editor crashes on ComputeShader::GatherProperties when enabling Frame Debugger
How to reproduce:
1. Open the user's attached project "renderdoc bug repro.zip"
2. Load the "SampleScene"
3. Go to Window > Analysis > Frame Debugger
4. Click on Enable in the Frame Debugger window
-- Observe the crash
Reproducible with: 2019.1.0a4, 2019.1.14f1, 2019.2.21f1, 2019.3.4f1, 2020.1.0a26, 2020.2.0a1
Not reproducible with: 2017.4.37f1, 2018.4.18f1, 2019.1.0a3
First top stack trace lines:
0x00007FF692857861 (Unity) ComputeShader::GatherProperties
0x00007FF692856B7C (Unity) ComputeShader::DispatchComputeShader
0x00007FF6924D5BF9 (Unity) RenderingCommandBuffer::ExecuteCommandBufferWithState
0x00007FF6924D4ABA (Unity) RenderingCommandBuffer::ExecuteCommandBuffer
0x00007FF692362E0A (Unity) ExecuteCommandBufferFromScriptImpl
<...>
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
- The Editor becomes unresponsive and memory allocation errors are spammed in the Console when Generating Lightning
- Crash on BatchApplyPropertiesFromSourceAssetDB when opening a specific project
- Scene view Camera cannot be moved with WASD/QE keys when the Right Mouse Button is held down and the Mouse is not moved
- Crash when calling default interface method from virtual method with same name
- [Android] Unity does not include the ".aab" extension for an AppBundle when it is built via script with the buildPlayerOptions.locationPathName = "AppName.apk" and EditorUserBuildSettings.buildAppBundle = true
Resolution Note (fix version 2020.2):
Fixed in: 20202.2.0a3
Resolution Note (fix version 2020.1):
Fixed in: 2020.1.0b2
Resolution Note (fix version 2019.3):
Fixed in: 2019.3.7f1