Skip to content
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

Open
robinvd opened this issue Mar 30, 2018 · 4 comments
Open

Zombie processes #32

robinvd opened this issue Mar 30, 2018 · 4 comments

Comments

@robinvd
Copy link

robinvd commented Mar 30, 2018

After running a command, a zombie process stays.

32430 robin     20   0  127208   4812   3068 S   0.0  0.0   0:00.24                          `- bash                                                                                                                                                                                        
23581 robin     20   0  1.001t  34584  30164 S   0.0  0.3   0:00.09                              `- sos                                                                                                                                                                                     
23661 robin     20   0       0      0      0 Z   0.0  0.0   0:00.04                                  `- cabal                                                                                                                                                                               
24087 robin     20   0       0      0      0 Z   0.0  0.0   0:00.04                                  `- cabal                                                                                                                                                                               
24213 robin     20   0       0      0      0 Z   0.0  0.0   0:00.05                                  `- cabal

im using Steel Overseer 2.0.1.0
and the command sos -p '.*\.hs' -c 'cabal run'

@schell
Copy link
Owner

schell commented Mar 30, 2018

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.

@schell schell closed this as completed Mar 30, 2018
@schell schell reopened this Mar 30, 2018
@mitchellwrosen
Copy link
Collaborator

mitchellwrosen commented Mar 30, 2018

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?

@schell
Copy link
Owner

schell commented Mar 30, 2018

@mitchellwrosen sounds plausible.
@robinvd what was sos's output after the command ran?

@robinvd
Copy link
Author

robinvd commented Mar 30, 2018

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants