Search Issue Tracker
Fixed
Votes
0
Found in
2019.3.0b10
2019.3.13f1
2020.1
Issue ID
1248909
Regression
Yes
[Vulkan] Crash on vk_optimusGetInstanceProcAddr when double clicking shader's Compiled Code drop down arrow
Reproduction steps:
1. Open the attached "case_1248909_zip" project
2. Select the "Settings\ssao" shader in the Project window
3. Double click on the arrow next to "Compile and show code" in the Inspector window
-- Observe the crash
Reproducible with: 2019.3.0b10, 2019.3.16f1, 2020.1.0a24
Not reproducible with: 2018.4.23f1, 2019.3.0b9
Notes:
- an error message appears before the crash: "Missing Vulkan framebuffer attachment image? (Filename: Line: 0)"
- was not able to reproduce the issue without URP package
Top 5 lines of the stack trace:
0x00007FFCD3868882 (nvoglv64) vk_optimusGetInstanceProcAddr
0x00007FFCD3868773 (nvoglv64) vk_optimusGetInstanceProcAddr
0x00007FFCD37EE6D8 (nvoglv64) vkGetInstanceProcAddr
0x00007FF70526ABCD (Unity) vk::TaskExecutor::FlushRenderPass
0x00007FF70526B185 (Unity) vk::TaskExecutor::HandleCommandStream
<...>
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 first frames are skipped when playing a video
- Text auto-scrolling can not work when naming assets/objects until backspace key is pressed
- Shadows are not cast when the Light's CullingMask and the GameObject's Layer do not match
- Graphics.DrawMeshInstanced does not work when 2D Renderer and 2D Shaders are used
- SpeedTree does not move when using WindZone
Resolution Note:
Fixed in: 2020.1.0a25