[asterisk-bugs] [Asterisk 0011698]: Segmentation fault / Memory corruption with intensive AMI

noreply at bugs.digium.com noreply at bugs.digium.com
Wed Jan 9 05:11:42 CST 2008


A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=11698 
====================================================================== 
Reported By:                Callmewind
Assigned To:                Corydon76
====================================================================== 
Project:                    Asterisk
Issue ID:                   11698
Category:                   Core-General
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     feedback
Asterisk Version:           1.4.16.2 
SVN Branch (only for SVN checkouts, not tarball releases):  1.4  
SVN Revision (number only!):  
Disclaimer on File?:        N/A 
Request Review:              
====================================================================== 
Date Submitted:             01-07-2008 04:19 CST
Last Modified:              01-09-2008 05:11 CST
====================================================================== 
Summary:                    Segmentation fault / Memory corruption with
intensive AMI
Description: 
We've developed an application which uses intensively AMI, specially
Redirect actions and UserEvents. We are using only SIP channels.
Asterisk crashes randomly, one time at day, with 10-15 calls.
So we build some kind of test system with 2 Asterisk, one making calls to
the other, and it crashes at 30 minutes or so.
====================================================================== 

---------------------------------------------------------------------- 
 Callmewind - 01-09-08 05:11  
---------------------------------------------------------------------- 
Bad news,
today I upgraded to last 1.4 svn and it crashed again.
I've tested three times:
-The first time asterisk didn't crash but stopped accepting new calls and
registration from the other asterisk of the test.
-Second time it crashed with a segmentation fault
-Third time I re-ran asterisk with valgrind until crashed.
I will upload valgrind outputs from the last crash and, if you want, I can
upload backtraces too. 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
01-09-08 05:11  Callmewind     Note Added: 0076544                          
======================================================================




More information about the asterisk-bugs mailing list