Search Issue Tracker
Fixed in 2020.2.X
Fixed in 2020.1.X
Votes
0
Found in
2020.1.0a16
2020.2
2020.2.0a5
Issue ID
1231120
Regression
Yes
Crash on GetCompiledComputeShaderCode when clicking "Show compiled code" of a Compute Shader
How to reproduce:
1. Open the attached "fp16Test" project
3. In the Project window, select "NewComputeShader"
4. In the Inspector window, click "Show compiled code"
5. Observe the crash
Reproducible with: 2020.1.0a16, 2020.1.0b4, 2020.2.0a5
Not reproducible with: 2019.3.0a10, 2019.3.7f1, 2020.1.0a1, 2020.1.0a15
Could not test with: 2017.4.38f1, 2018.4.20f1, 2019.2.21f1, 2019.3.0a9 due to URP not being available for the shader
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
- APV data is sometimes incorrectly loaded from multiple baking sets when loading a scene
- GC Alloc spikes occur when calling UnityEngine.Resolution and UnityEngine.RefreshRate with Equals() and GetHashCode()
- Type error is thrown when a new ComputeShader is instantiated after destroying previous ComputeShader
- APV data becomes incorrect when reselecting the currently active Baking Set
- Launch screen image exceeds the screen bounds on IPad when building for iOS
Resolution Note (fix version 2020.2):
Fixed in 2020.2.0a8