-
Notifications
You must be signed in to change notification settings - Fork 969
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
Segmentation fault running example #2789
Comments
Thanks for filling, nothing off to my eye in the log. Could you try to get a backtrace from the segmentation fault using gdb? Some other possible causes - if you have the vulkan validation layers installed, make sure they are up to date, versions before 1.2.180 or so can easily segfault. |
Backtrace:
The vulkan packages I use:
|
Are you using renderdoc? Is it up to date? |
I do have it installed:
I don't know why this would cause a segfault. |
Is the backtrace saying the segfault comes from trying to open |
Yeah, that's what it looks like to me |
Is there any next step I can do? I have never used |
I think this is an issue with librenderdoc.so - I suspect you're only supposed to load it while renderdoc is attached. Clarifying this with baldurk... |
We aren't loading renderdoc correctly - I'm going to file a new issue about that and close this one. Thank you for the report! In the mean time, the best route would be to try to hide renderdoc from your application - not sure exactly how to do this on your system. |
Closed in favor of #2793 |
Description
Tried to run any example, but causes segfault
Repro steps
Clone repo, checkout
0.12.0
, try to run any example (cube, hello-compute, etc):Expected vs observed behavior
Expected: example runs
Observed: segmentation fault
Extra materials
Look at attachment
trace.log
Platform
Pop OS 22.04, Intel UHD, Vulkan:
The text was updated successfully, but these errors were encountered: