[asterisk-bugs] [Asterisk 0014043]: Crash (included coredump)
Asterisk Bug Tracker
noreply at bugs.digium.com
Thu Jan 29 16:35:00 CST 2009
A NOTE has been added to this issue.
======================================================================
http://bugs.digium.com/view.php?id=14043
======================================================================
Reported By: ibc
Assigned To: putnopvut
======================================================================
Project: Asterisk
Issue ID: 14043
Category: General
Reproducibility: unable to reproduce
Severity: block
Priority: normal
Status: assigned
Asterisk Version: 1.4.22
Regression: No
SVN Branch (only for SVN checkouts, not tarball releases): N/A
SVN Revision (number only!):
Request Review:
======================================================================
Date Submitted: 2008-12-09 12:04 CST
Last Modified: 2009-01-29 16:34 CST
======================================================================
Summary: Crash (included coredump)
Description:
Asterisk 1.4.22 has crashed when handling around 60 SIP channels. This
server supports usually much more traffic (~ 500 SIP channels).
Before 1.4.22 version, this error (crash) occurred very often during the
max calls period (once each 2 days). That error seemed to be fixed in
1.4.22, until now. Of course, it could be a very different issue.
There are not Zap devices, just SIP users and SIP trunks.
We do CDR against an external MySQL server via ODBC and use dynamic
realtime dialplan.
GDB output is attached.
======================================================================
Relationships ID Summary
----------------------------------------------------------------------
related to 0014060 [patch] Astrerisk crashes using the app...
related to 0014086 Address out of bounds in queue_log usin...
======================================================================
----------------------------------------------------------------------
(0099100) putnopvut (administrator) - 2009-01-29 16:34
http://bugs.digium.com/view.php?id=14043#c99100
----------------------------------------------------------------------
ibc's valgrind output is showing the same sort of invalid memory access to
a freed datastore that was seen in issue
http://bugs.digium.com/view.php?id=14086. At this point, I'll take
just a single confirmation that the patches there fix your problems,
because I am now 99.999% sure that these are the same problem.
Issue History
Date Modified Username Field Change
======================================================================
2009-01-29 16:34 putnopvut Note Added: 0099100
======================================================================
More information about the asterisk-bugs
mailing list