You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Not much can be done for SIGKILL, but for SIGTERM I can certainly have it try to terminate the game process as well, at least for games not launched through Steam (since I don't have direct control over those).
I vaguely remember ctrl-c working to kill the game process on my system? Could've just been my imagination, but I'll look into it nonetheless.
After staring a game with
tcli run
, thetcli
process will orphan the game process upon termination.Expected Behavior
After running a game with
tcli run
, terminating thetcli
process (e.g.Ctrl+C
,SIGTERM
/SIGKILL
) should also terminate the game process.Current Behavior
The game process remains running as an orphan process after the
tcli run
process is terminated.Steps to Reproduce
tcli
e.g.tcli.exe run {game identifier}
tcli
and game process are running:tcli
process (e.g. pressingCtrl+C
in a shell or sendingSIGTERM
/SIGKILL
withkill
)tcli
process is terminated, but the game process is running and orphaned:Workaround
Manually terminate the game process with
kill
e.g.kill 142929
in example above.Context (Environment)
Running
tcli 0.2.0
withtcli-bepinex-installer 0.1.0
(compiled with an olderglibc
version) on Debian GNU/Linux 11 (bullseye)The text was updated successfully, but these errors were encountered: