-
-
Notifications
You must be signed in to change notification settings - Fork 21.2k
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
Vulkan: Crash has caused persistent vkEnumeratePhysicalDevices failure #60755
Comments
Same hardware, different OS (Pop!_OS 22.04 LTS 64 bit). An instance of alpha 8 left running on suspend freezes* when the computer is woken up again. The terminal endlessly prints
until I force quit the program. * I've had some different behaviours - generally it's completely unresponsive, but one time trying to close the window by clicking x brought up the "unsaved changes" confirmation dialog (I assume - the dialog itself was displaying a snaphsot of what the screen had previously been displaying). With some lucky clicking, I managed to quit out of the program using this dialog. So far, I haven't had any issues when restarting Godot, and it runs as usual. On this OS, seems to be the same behaviour reported in #52738. |
@snailrhymer Do you happen to have an AMD cpu/apu with integrated graphics? It could be a duplicate issue to #57708 where your system is confused between integrated graphics options and pci gpus. |
I have the same issue as @snailrhymer, I do this:
I use Godot 4 beta 17 (64 bits) for now, this happened with all others beta release AFAIK. This behavior on wake up remind me some older program I've used (I think it's zModeler, a shareware 3D modeler specifically made for using with rFactor/GTR2 racing sims), on the other end, a program like 3DSMax (2011 & 2015) never have such kind of issue as far as I can remember. Something which is worth to be tested: this issue can also happen when using a 3D game in fullscreen mode. It may be related to the way low-level device context is setup. |
Do you have the runtime error or just the swapchain errors? I recall another report of Godot editor not reacting properly on wakeup... |
Only the swapchain error. |
Yes, I've got an AMD cpu - looks like this is indeed a duplicate of #57708. I haven't tried any driver updates as suggested in that thread, and can confirm that Still with no driver updates, the editor binary from #73450 does work! 🎉 |
Godot version
v4.0.alpha7.official.3e9ead05f
System information
Windows 10, Vulkan, nvidia geforce gtx 1660Ti
Issue description
In summary, I've previously been able to run 4.0 alphas up to and including 7, as well as various custom builds. One of my custom builds crashed and now I can't run any version of 4.0.
I left a custom build running when I put my computer to sleep. The build crashed on waking up. I didn't think this was too exceptional, so don't remeber what errors, if any, were shown. I then compiled the build with a minor change and tried to run it (using
-e
to open a project directly), which produced this error popup:Now I can no longer run the official alphas either - they produce the same error before reaching the project manager. Running from the command line additionally gives
Following the advice in #58927, I've run alpha7 with
--rendering-driver opengl3
and--single-window
. This lets me open the project manager, but I get the same crash as usual when I try to open any project (including a newly created one). Output:(where I've skipped some lines of repeated error messages).
I've restarted/updated my drivers, but the problem persists. The custom build I was running only contained fairly simple changes to how tab history is saved in the editor, so I imagine the cause of the problem was the crash after waking up from sleep.
Steps to reproduce
I can't reproduce whatever caused the initial crash, because 4.0 won't run at all for me any more.
Minimal reproduction project
No response
The text was updated successfully, but these errors were encountered: