[asterisk-bugs] [Asterisk 0011698]: Segmentation fault / Memory corruption with intensive AMI
noreply at bugs.digium.com
noreply at bugs.digium.com
Thu Jan 10 03:03:31 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-10-2008 03:03 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-10-08 03:03
----------------------------------------------------------------------
No luck :(
It crashed again. New valgrind3.txt and malloc_debug3.txt files.
As a comment, I've tried a similar test but using AMI only to generate
calls and hangup some of them, and the rest of the logic implemented via
fastAgi (basically play tt-monkeys in both ways of the call) and it crashed
too.
Another comment: if we run the test with 2 asterisk in the local network
it crashes around ten minutes; and if we run it across internet it can take
several hours to crash.
Issue History
Date Modified Username Field Change
======================================================================
01-10-08 03:03 Callmewind Note Added: 0076622
======================================================================
More information about the asterisk-bugs
mailing list