-
-
Notifications
You must be signed in to change notification settings - Fork 156
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
[winewayland.drv] "GameThread timed out waiting for RenderThread" (crash/freeze) in Sway #1147
Comments
That log output doesn't seem to come from wine and it seems to be the game timing out, which would point to Sway handling of the window being the issue here. I assume it works fine with xwayland/winex11.drv ? |
Yes that's correct, I can't reproduce this with XWayland driver in WINE. My apologies for the confusion, the stacktrace is different or non existent depending on which game is tested (as you guessed). The one posted above was for With Terminal:
Dialog:
|
Do you happen to be using an NVIDIA graphics card with the proprietary driver? This issue may not be specific to sway. I'm not on sway (I'm on wayland GNOME), but had this issue on the native wayland driver (but not on the x11 driver) with a couple of games when I was on an NVIDIA GPU. It went away when I switched to an AMD GPU. For me, games on the native wayland driver would basically semi-regularly but randomly freeze until I inputted something on the window (e.g. I clicked inside the game window or pressed a key). If it didn't input anything and just let it stay frozen, the game would time out after two minutes as you describe. I'd be as if the game would randomly unfocus (and thus stop rendering), even though I was playing it and wasn't alt-tabbed or anything. Although, every now and then if I was "unlucky" it would hard freeze and no inputs would unfreeze the game - I'd have to kill the process through command line or something. |
I'm using 7900 XT and I've also been able to reproduce this with 6800 XT
There's some Reddit posts claiming to have the same issue with KDE too Although I know that Sway doesn't render anything inside Workplaces which are unfocused. If you play a Youtube video in one workplace and switch to another, when you come back it will show you the last rendered frame before rendering a new one |
To repeat what I've commented on upstream bug: XWayland works this around by rendering frames once in a while even when rendering callback is not being invoked by Wayland compositor, exactly to prevent this kind of issues arising in X applications (which includes Wine under XWayland). Since Windows apps evidently also rely on rendering continuing to run at all times, Wine could fix this in its Wayland driver by also rendering frames once in a while (e.g. once per second) when app is invisible. |
This issue isn't specific to
wine-tkg
My upstream bug report #56172 has been stale for weeks and I was hoping there's someone experienced here who can give advice on how to resolve this issue :)
Problem
_wayland_driver="true"
) withSway 1.9
.Stacktrace
Detroit Become Human:
LowLevelFatalError [File:Unknown] [Line: 1209] GameThread timed out waiting for RenderThread after 120.00 secs
Question
Can I somehow disable the 120 seconds timeout / is there's any proper method to resolve this issue?
The text was updated successfully, but these errors were encountered: