[asterisk-bugs] [Asterisk 0012648]: [patch] Asterisk leaves zombie agi processes when running under linux 2.6

[noreply at bugs.digium.com]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=12648 
====================================================================== 
Reported By:                gkloepfer
Assigned To:                Corydon76
====================================================================== 
Project:                    Asterisk
Issue ID:                   12648
Category:                   Resources/res_agi
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     assigned
Asterisk Version:           1.4.19 
SVN Branch (only for SVN checkouts, not tarball releases):  1.4  
SVN Revision (number only!): 115937 
Disclaimer on File?:        N/A 
Request Review:              
====================================================================== 
Date Submitted:             05-14-2008 12:06 CDT
Last Modified:              05-14-2008 16:24 CDT
====================================================================== 
Summary:                    [patch] Asterisk leaves zombie agi processes when
running under linux 2.6
Description: 
[Note: re-open, duplicate of Problem ID 0005238]

I have actually found a way to duplicate this bug.  If a long-running AGI
script is executing by one user and another user hangs-up on an AGI script,
a zombie will be left running.  This can be duplicated by using the
following dialplan code:

exten =>_X.,1,Answer
exten =>_X.,n,AGI(time-request.agi)
exten =>_X.,n,Hangup

(time-request.agi is an AGI script that says the time every 10 seconds
until the user hangs-up or presses a button on the keypad ... any
long-running AGI script like this should work).
====================================================================== 

---------------------------------------------------------------------- 
 gkloepfer - 05-14-08 16:24  
---------------------------------------------------------------------- 
Just keep multiprocessor issues in mind.  The person who wrote sysvinit
made an assumption that a process context switch would provide some delay
for the child to do some work, and it turns out that both processes were
running simultaneously with >1 CPU which broke that assumption
(http://bugs.gentoo.org/show_bug.cgi?id=188262).

The good news is that in the worst case we'll just have a few zombie
processes that will eventually get cleaned-up. 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
05-14-08 16:24  gkloepfer      Note Added: 0086878                          
======================================================================