-
Notifications
You must be signed in to change notification settings - Fork 15
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Zombie processes #32
Comments
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. |
im running nixos.
@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 command
sos -p '.*\.hs' -c 'cabal run'
The text was updated successfully, but these errors were encountered: