den_RDC wrote:A zombie process is already dead and exit'ed. You cannot kill it again. The zombie process
I already nagged about this on irct, but i have collected some log output.
The problem is the following : Freevo (1.4) kill's mplayer (with dfbmga) always the hard way when playing video. Playing audio files doesn't show any problem. I investigated this and made the following observations.
- Killing mplayer manually from the shell (but started by freevo!) works perfectly.
you mean kill -15?
- Although mplayer is single-threaded afaik, with dfbmga it does use multiple threads (mostly 4 or 5, this seem to fluxtuate, dunno why).
- After freevo hardkills mplayer, a zombie mplayer process is left over.
Freevo does
1. send 'quit' to mplayer 2. kill -15 3. kill -9
- No real side-effects for the user, although he has to wait 2 seconds after pressing stop or back before the menu shows up (because of the repeated polling in childapp)
Because kill -9 is the _last_ chance to get rid of the program, but I
don't understand why a zombie still survives all this.
is waiting in the process list until the parent (freevo in this case) has checked its return status.
You can get rid of the zombie by catching SIGCHLD or by calling the wait() function,
see manpages signal(2) and wait(2).
- Richard.
------------------------------------------------------- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ _______________________________________________ Freevo-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freevo-devel
