-
Notifications
You must be signed in to change notification settings - Fork 68
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Launching with Vulkan driver causes a segfault #165
Comments
Loads fine with Vulkan + "Allow Cores to Switch the Video Driver" OFF on Windows 10 at least. |
I also have got the same issue on Manjaro (Arch Linux) with an Intel iGPU using mesa driver. |
Same issue cf6ca2a47f Vega 56, MESA Two other cores I have loaded up, and stand alone dolphin emulator works fine with Vulkan. Works in GL. |
Seems this might be an amdgpu issue. I'm experiencing the same issue here as well. Works fine in GL (but slower), segfaults as soon as launched with vulkan. Standalone dolphin does Vulkan fine as well. All I get GLX reporting invalid screen size results, and then the app crashes. here's a dump: https://hastebin.com/wuzediwone.sql |
Libretro dolphin also crashes on my system.
Setting retroarch
The vulkan renderer does work for other libretro backends. Getting a backtrace by gdb gave me no interesting results due to debug symbols missing. Please instruct me if more information is needed. |
Arch Linux with Intel graphics. OpenGL works fine. I was able to get a backtrace out of
segfault happens at Here's the backtrace in gdb:
|
Same issue, Lakka nightly Generic x86.
|
I can't reproduce the issue with nvidia driver under Xorg. I tested with with homebrew Super Methane Brothers from content downloader. So the issue will be related to Wayland and/or DRM/KMS only ? |
I can reproduce with KMS/Intel (Lakka) and Xorg/AMD (Arch). Same backtrace. It sounds like this might be everything but nVidia? |
It's probably not Wayland since I wasn't using Wayland at the time of encountering the bug. |
Alright I reproduced the issue using Intel HD and Vulkan. Here is the backtrace
|
The check at
vkGetPhysicalDeviceProperties2 is non-null (if it was null, we'd return on a short circuit evaluation of the statement there).
Your stack trace seems to indicate that gpu is also non-null, and the other argument to My best conclusion is that |
Just reporting that I’m experiencing this problem as well, on the latest master (3b19e6d). OS: Fedora 35 The GL driver seems to work fine. |
Here is the log with Vulkan Validation Layers using
|
@RobertTheSable The issue should be renamed to It seems vkGetPhysicalDeviceProperties2 is coming from Vulkan 1.1 but we are using Vulkan 1.0 context ? But why it would work with Nvidia Vulkan driver ? |
Verified this on the steam version on steam deck. Seems like it should be as simple as switching to requesting a 1.1 context then, right? Or am I missing something? |
I confirm this issue is fixed with this PR. So running latest master or future RA 1.15.0 will fix this issue. |
@RobertTheSable Please close this issue as it has been fixed. Thank you. Kind regards, |
Launching Dolphin build from the current master (f4f4947) with the Vulkan driver enabled and core driver switching disabled results in a segfault.
The driver appears to have been broken by the 5.0 rebase, as the last commit I can verify it worked on was cf6c736.
I'm running on Kubuntu 20.04 with an AMD Radeon RX 480 GPU, using the amdgpu driver. I'm not sure if it's a Linux specific issue or not.
The text was updated successfully, but these errors were encountered: