Search Issue Tracker
Fixed
Fixed in 6000.0.3f1
Votes
0
Found in
2022.3.20f1
2023.2.11f1
2023.3.0b8
6000.0.0b11
Issue ID
UUM-64372
Regression
No
Crash on "vkGetInstanceProcAddr" when attaching the Unity Editor process to RenderDoc
How to reproduce:
1. Install RenderDoc and open it
2. Open the attached “IN-68704” Project
3. Right-Click on the Scene View tab (or press on the “kebab” button)
4. Press the “Load RenderDoc” button
Expected result: The Unity process gets attached to the RenderDoc
Actual result: Unity crashes
Reproducible with: 2022.3.20f1, 2023.2.11f1, 2023.3.0b8
Couldn’t test with: 2021.3.35f1 (Compilation errors, more information in the “Notes” section)
Reproduced on: Windows 11 (22H2), Windows 10 (by user)
Notes:
- Not reproducible on a new Project
- In 2021.3.35f1 after pressing the “Load RenderDoc” button it would appear nothing happened and the button dissapears however cannot verify if this is a “couldn’t test with” situation or a “Not Reproducible” situation, as compilation errors are present which may be the cause for the crash not happening
First few lines of Stack Trace:
0x00007FF9FD471965 (nvoglv64) vkGetInstanceProcAddr
0x00007FF9FD47338A (nvoglv64) vkGetInstanceProcAddr
0x00007FF8E17C8123 (renderdoc) VK_LAYER_RENDERDOC_CaptureNegotiateLoaderLayerInterfaceVersion
ERROR: SymGetSymFromAddr64, GetLastError: 'Attempt to access invalid address.' (Address: 00007FF973CA5AD2)
0x00007FF973CA5AD2 (Unity) (function-name not available)
ERROR: SymGetSymFromAddr64, GetLastError: 'Attempt to access invalid address.' (Address: 00007FF973C9F043)
0x00007FF973C9F043 (Unity) (function-name not available)
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- The layout system is failing to correctly calculate or apply the height of the Japanese fallback font when the primary English font's metrics are used
Add comment