Frama-C Bug Tracking System - Frama-C
View Issue Details
0002154Frama-CPlug-in > wppublic2015-09-01 21:302016-06-21 14:08
kroeckx 
correnson 
normalminoralways
closedfixed 
Frama-C Sodium 
Frama-C Aluminium 
0002154: Zombie processes
I'm starting it using: frama-c-gui -wp -wp-rte -wp-proof alt-ergo There are lots of goals, and some take a long time to run. I end up with lots of zombie processes. The number of zombie processes matches the number of "interrupted" in the summary. For some reason it's not cleaning up those properly.
No tags attached.
related to 0002132closed correnson Under windows, many times, Frama-c wp process doesn't kill alt-ergo process before finishing 
Issue History
2015-09-01 21:30kroeckxNew Issue
2015-09-02 09:47yakobowskiNote Added: 0006015
2015-09-02 09:47yakobowskiCategoryKernel => Plug-in > wp
2015-09-02 09:47yakobowskiAssigned To => correnson
2015-09-02 09:47yakobowskiStatusnew => assigned
2015-09-02 10:06corrensonRelationship addedrelated to 0002132
2015-09-02 18:30kroeckxNote Added: 0006017
2015-10-28 10:46corrensonNote Added: 0006091
2015-10-28 10:46corrensonStatusassigned => acknowledged
2015-11-25 15:37corrensonStatusacknowledged => resolved
2015-11-25 15:37corrensonFixed in Version => Frama-C Aluminium
2015-11-25 15:37corrensonResolutionopen => fixed
2016-06-21 14:08signolesStatusresolved => closed

Notes
(0006015)
yakobowski   
2015-09-02 09:47   
Can you give us some additional on the OS you are using?
(0006017)
kroeckx   
2015-09-02 18:30   
I'm using Debian testing on an amd64, but I assume at least all POSIX will have the issue. Please note that it's not like the related windows issue. The process has exited but still exist. It's just still has some status information kept with it that the parent could ask for like it's exit status. The process itself isn't using an CPU or memory anymore. When the parent doesn't care about it anymore it should clean it up. When a child exits you get send a SIGCHLD signal. You can then still ask for that status information about the child using functions like wait() and waitpid(), which will also clean it up. If you don't care about the exit status you can use signal() to say to ignore SIGCHLD and the kernel will then automatically clean it up.
(0006091)
correnson   
2015-10-28 10:46   
The bug have been isolated.