Open robinvd opened 6 years ago
Thanks for the issue. What OS are you running? Does this happen on exit (ctrl-c) or during program execution? It looks like the latter. Maybe some better thread handling is in order.
If process A (steeloverseer) runs command B (cabal run) which itself spawns something (C) and then exits, C becomes a zombie. In this case it's B's job to wait on all of its children, not A's.
Is it possible that's what's going on here?
@mitchellwrosen sounds plausible.
@robinvd what was sos
's output after the command ran?
im running nixos. after a file change
Added: src/Emit.hs~
[1/1] cabal run
(bunch of cabal and program output)
Success ✓
@mitchellwrosen that could be, but in top cabal is a direct child of sos
After running a command, a zombie process stays.
im using
Steel Overseer 2.0.1.0
and the commandsos -p '.*\.hs' -c 'cabal run'