[asterisk-bugs] [Asterisk 0011698]: Segmentation fault / Memory corruption with intensive AMI
noreply at bugs.digium.com
noreply at bugs.digium.com
Thu Jan 17 05:34:54 CST 2008
A NOTE has been added to this issue.
======================================================================
http://bugs.digium.com/view.php?id=11698
======================================================================
Reported By: Callmewind
Assigned To: russell
======================================================================
Project: Asterisk
Issue ID: 11698
Category: Core-General
Reproducibility: always
Severity: minor
Priority: normal
Status: assigned
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-17-2008 05:34 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-17-08 05:34
----------------------------------------------------------------------
Ok, finally I could checkout the new code; I ran it but it crashed again.
With debugger it crashed but no core dump was generated. New valgrind5.txt
and malloc_debug5.txt uploaded.
Issue History
Date Modified Username Field Change
======================================================================
01-17-08 05:34 Callmewind Note Added: 0080804
======================================================================
More information about the asterisk-bugs
mailing list