[asterisk-bugs] [Asterisk 0011601]: crashes with "*** glibc detected *** corrupted double-linked list" with connections to asterisk manager

[noreply at bugs.digium.com]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=11601 
====================================================================== 
Reported By:                rolek
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   11601
Category:                   Core-General
Reproducibility:            always
Severity:                   crash
Priority:                   normal
Status:                     new
Asterisk Version:           1.4.15  
SVN Branch (only for SVN checkouts, not tarball releases): N/A  
SVN Revision (number only!):  
Disclaimer on File?:        N/A 
Request Review:              
====================================================================== 
Date Submitted:             12-19-2007 10:34 CST
Last Modified:              12-19-2007 10:46 CST
====================================================================== 
Summary:                    crashes with "*** glibc detected *** corrupted
double-linked list" with connections to asterisk manager
Description: 
I'm running asterisk 1.4.x with a IAX uplink and some SIP phones.
Essentially, this works fine. However, when making connections to the
asterisk manager interface [from a php application, in a certain timed
fashion], asterisk crashes while showing a notice like:
*** glibc detected *** corrupted double-linked list: 0x081cb7e0 ***
This happens reproducibly on three different boxes, all with different
hardware.
====================================================================== 

---------------------------------------------------------------------- 
 rolek - 12-19-07 10:46  
---------------------------------------------------------------------- 
The php code that is making the connection does two relatively simple
things (example in pseudo code):

open socket
write to socket "Action: login"
read output
write to socket: "show channels"
read output
write to socket: "Action: Logoff"
read output
close socket

The second command sequence has a similar structure but runs the 'database
show' command.
The thing that really bothers me is that if we run this every second or
faster, the problem does not appear. However, if we run it every 5 seconds,
the problems occur and asterisk crashes, often within 10 minutes from
starting. 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
12-19-07 10:46  rolek          Note Added: 0075707                          
======================================================================