Client process keeps running after its window is closed
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 55/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Active
- Domain
- game-dev, operating-systems
Research direction
Reproduce the issue with a single game using launch-client.sh at main @ a53e0c5, then inspect /proc//task/*/comm or a stack dump after closing the window. Check the runtime shutdown log for PerformGracefulShutdown; done means identifying which threads keep echovr.exe alive and whether the graceful-shutdown path runs.
Written by the indexing model from the issue text.
Description
Observed 2026-09-30 running the client in a nested Xephyr display (launch-client.sh, Wine, main @ a53e0c5): after the owner closed the game windows, both echovr.exe processes were still running until they were sent SIGTERM.
Evidence (ps -eo pid,etime,args after the owner reported closing the window): 793 19:53 ./echovr.exe -noovr -windowed -mp and 81341 04:41 ./echovr.exe -noovr -windowed -mp, each with its launch-client.sh still waiting on it. Sending SIGTERM to the newer game (81341) made its script finish normally (PASS, DLL restored); the older game (793) was gone at the same time (the script's cleanup runs wineserver -k).
Not established: which window the owner closed, whether the game was still in a session, and what keeps the process alive (a runtime worker thread, the bridge listener, token refresh, UPnP/telemetry/mic threads, or Wine itself). The runtime has a graceful-shutdown path (PerformGracefulShutdown); whether it runs on a window close is unverified.
To do: reproduce with a single game, close the window, and record which threads remain (/proc/<pid>/task/*/comm or a stack dump) and the runtime's own shutdown log lines.
- Dominant language
- C++
- Stars
- 2
- Forks
- 3
- Avg merge
- 9h 6m
- Merged PRs (30d)
- 459
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from EchoTools/nevr-runtime
-
backlog
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
EchoTools/nevr-runtime#957 ·
Maintainers usually reply within 1 day
-
documentation
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
EchoTools/nevr-runtime#892 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
EchoTools/nevr-runtime#889 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
EchoTools/nevr-runtime#801 · 1 comment ·
Maintainers usually reply within 1 day
-
backlog
Difficulty 2/5 1-3 hours Newbie friendliness 83/100
EchoTools/nevr-runtime#796 ·
Maintainers usually reply within 1 day
All issues in EchoTools/nevr-runtime
Similar issues
-
Status: Needs confirmation Status: Needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
Maintainers usually reply within 1 day
-
bug-unconfirmed
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 1 day
-
A-combat P-low S-ready-to-start task
Difficulty 2/5 1-3 hours Newbie friendliness 77/100
Maintainers usually reply within 1 day
-
bug intrinsic medium priority rt_lib
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Maintainers usually reply within 1 day