[Bug 59742] New: winedevice.exe never exits
http://bugs.winehq.org/show_bug.cgi?id=59742 Bug ID: 59742 Summary: winedevice.exe never exits Product: Wine Version: 11.0 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs@list.winehq.org Reporter: hugo@whynothugo.nl Distribution: --- I'm running some games via: gamescope -W 3440 -H 1440 wine path/to/game.exe gamescope renders a nested compositor, and wine runs inside of it. Typically, gamescope exits whenever its child process exits. However, with this setup, gamescope never exits, because its child never exits. When the game exits, a winedevice.exe process lingers, forever. Gamescope perceives that its child is still running and does not exist. winedevice.exe should exit when the main `game.exe` (in this example) exits, or when all wine processes exit. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=59742 --- Comment #1 from Hugo Osvaldo Barrera <hugo@whynothugo.nl> --- Created attachment 80915 --> http://bugs.winehq.org/attachment.cgi?id=80915 Process tree after game.exe has exited -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=59742 Stian Low <wineryyyyy@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |wineryyyyy@gmail.com --- Comment #2 from Stian Low <wineryyyyy@gmail.com> --- Also seen this for some games without running any via gamescope. Recently noticed multiple winedevice.exe processes remain open while testing Foundation Galactic Frontier: https://bugs.winehq.org/show_bug.cgi?id=59248 At first I thought it was just an issue with this game because it seems to launch background services as if meant to linger including producing a separate window with a game icon that appears intended for systemtray. The game cannot be reliably tested for different rendering backends and Windows versions without killing the winedevice.exe processes; otherwise the previous state is loaded. Since that game brought winedevice.exe to my attention I've been trying to pay closer attention to its behavior for other games some of which I've noticed also keeping windevice.exe open. I mean to take a closer look but haven't had time yet. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=59742 Hugo Osvaldo Barrera <hugo@whynothugo.nl> changed: What |Removed |Added ---------------------------------------------------------------------------- Version|11.0 |11.5 CC| |leslie_alistair@hotmail.com | |, z.figura12@gmail.com Component|-unknown |-unknown Product|Wine |Wine-staging -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=59742 --- Comment #3 from Hugo Osvaldo Barrera <hugo@whynothugo.nl> --- Yeah, gamescope merely makes the issue blatantly obvious, but winedevice.exe lingers regardless. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=59742 Austin English <austinenglish@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |austinenglish@gmail.com -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=59742 Bernhard Übelacker <bernhardu@mailbox.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |bernhardu@mailbox.org --- Comment #4 from Bernhard Übelacker <bernhardu@mailbox.org> --- Can reproduce it with following, no extra application needed: gamescope wine winemine As a workaround the wine background processes could be started outside of gamescope: wine wineconsole cmd /c "timeout /t 2" & sleep 1s; gamescope wine winemine Unfortunately gamescope got not released with Debian Trixie, but the package from testing just after the release was installable at my system: https://snapshot.debian.org/archive/debian/20250811T030546Z/pool/contrib/g/g... -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=59742 --- Comment #5 from Bernhard Übelacker <bernhardu@mailbox.org> --- A probably better workaround: gamescope -- bash -c "wine winemine; wineserver -w" Is the problem wineserver gets killed before it can shutdown winedevic.exe? Kind of a variant of bug #57608? -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=59742 --- Comment #6 from Bernhard Übelacker <bernhardu@mailbox.org> --- (In reply to Bernhard Übelacker from comment #5)
Is the problem wineserver gets killed before it can shutdown winedevic.exe? Kind of a variant of bug #57608?
Following link to the source of gamescope seems to prove it actively makes sure forked childs get killed. https://github.com/ValveSoftware/gamescope/blob/master/src/Apps/gamescoperea... And having wineserver killed usually makes wine processes wait forever. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=59742 --- Comment #7 from Hugo Osvaldo Barrera <hugo@whynothugo.nl> --- The following workaround also works: wineserver # Never exits if created by a child of gamescope. gamescope … wine game.exe wineserver -k # Clean up explicitly. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=59742 --- Comment #8 from Bernhard Übelacker <bernhardu@mailbox.org> --- (In reply to Bernhard Übelacker from comment #6)
Following link to the source of gamescope seems to prove it actively makes sure forked childs get killed.
https://github.com/ValveSoftware/gamescope/blob/master/src/Apps/ gamescopereaper.cpp#L19
Just a short addition: If gamescope really kills wineserver, it is also responsible to kill winedevice.exe. So this can be seen as a bug in gamescope? -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
participants (1)
-
WineHQ Bugzilla