-
-
Notifications
You must be signed in to change notification settings - Fork 3.6k
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
Closing window doesn't end process #11811
Comments
I think you are using the AMDVLK driver. You might want to try the Mesa Radeon drivers, RADV. They are generally better supported. Try uninstalling the |
Switch to the
|
Happens with xwayland. When running on wayland with wayland feature enabled it works correctly, seems to be the same issue as you said |
It's interesting that (apparently/probably) since #11737 got merged, it now panics a second time. This is the full message:
That's why I didn't immediately recognize the error. |
I'm seeing the same original problem with the recommended drivers, hangs after closing without panic.
|
Seeing this same issue on Ubuntu after updating to 0.13 (was not an issue on 0.12.1):
After which the process hangs indefinitely until force-quit. |
gonna throw in my little insight, i have had this issue since 0.13 (on xwayland) as well, panicking when user closes the main window and also on |
Can confirm removing the |
another thing i just found out: having 2 games open, both with |
Same for me... (bevy 0.13.1 and 0.13.2) |
Duplicate of #10260. |
Fixed in #13236, can be closed. |
Bevy version
0.12.1
, as well as main at time of writing: b6945e5If your bug is rendering-related, copy the adapter info that appears when you run Bevy.
Tested the
winit
window
example and it works fineWhat you did
Ran any bevy app, for example the
sprite
example. Pressed theX
button in the top bar of the app.What went wrong
Process stayed open, had to be killed through
Ctrl+C
, or through system monitor.Expected: process closes.
Additional information
This happened both on Wayland and Xorg.
The text was updated successfully, but these errors were encountered: