mintty
mintty
Possibly related to #319? Could also be "BLODA".
It might also be related to cygwin's invisible console hack, as mentioned in mintty child.c: child_create. If so, someone with more expertise in cygwin/Windows interworking would be needed to debug...
Quoting a source comment in child.c: // Some native console programs require a console to be attached to the // process, otherwise they pop one up themselves, which is rather...
This looks like interesting information but to be honest, I cannot make a clue out of it. Maybe some of the cygwin gurus can see a pattern in this puzzle....
There may be a limit of conhost resources in Windows, don't know; why ssh-agent would need to be killed before starting another one seems quite unrelated, on the other hand.
It could also be that these conhost processes simply stay open on purpose, to serve as a container for the next conhost client application, like the svchost processes. Just speculating,...
Marking the issue as invalid as I don't see any way mintty could influence the behaviour.
So what is vscode? It does not seem to be cygwin-related...
This issue is about closing the conhost process, isn't it? So what's your issue? I can run `notepad &` or `notepad` from mintty and then start further mintty windows with...
Does it help to start your non-Cygwin, Windows application (Visual Studio) with `cygstart`? (Or setsid?)