Tabby doesn't terminate conhost process sometimes

[Funkmiser]

Version: 1.0.176 Platform: Windows x64 10.0.22000 Plugins: none Frontend: xterm

Description: Figured I might as well mention this issue as well, but sometimes when exiting Tabby I notice that the conhost process is still running in the detailed process tab under Task Manager. Basically from what I can tell when opening tabby from a folder (using shell integration) which opens up my default Powershell Core terminal and doing some commands (usually running a python program or two which modifies/creates files in the folder) if I exit out of Tabby completely by just clicking the X in the upper right then more often than not the conhost.exe process remains running. I usually find this out by trying to delete the folder and getting the 'This folder is being used by a process' dialog box. Whereas it seems that if I actually exit the terminal first by typing exit and having the tab close, then when closing tabby the conhost process does not remain running. My thought was that tabby was exiting faster than the command to close the conhost process could be sent/finished or something. I have the experimental ConPTY API option enabled all the time as a side note.

Testing: I just tested it by creating a New Folder on my desktop, opening tabby in it and then exiting tabby using the X in the upper right and I see that conhost remains in my process list but I could still delete the folder, but that might be because I didn't use a command that touched or modified any files. When it does block me from deleting the folder I found that if I end the conhost process using task manager I am able to delete the folder. It does seem that doing the exact same test but typing 'exit' to close the terminal tab closes both the pwsh process and conhost process, though the tab takes like 20 seconds to close after hitting enter. Maybe a second or two to blank the text and then 10 to 15 seconds to actually close the tab. I use a custom profile for my Powershell that imports some modules so that might be why it takes a bit to close.

[Tzeny]

I also have the same problem, if I ssh into a remote machine and close the Tabby tab, I can see that the process is still open. Have you found a fix?

[acmlau]

I noticed that using ctrl+a, ctrl+d to get out of ssh gives me the "init still running" error when closing Tabby. When I use "logout" on the commandline when I am done on the remote machine it doesn't. Maybe this solves your problem as well? @Tzeny