[asterisk-bugs] [Asterisk 0014945]: Abort in free() in local_hangup, possibly related to failure to provide ringback indication
Asterisk Bug Tracker
noreply at bugs.digium.com
Mon Apr 27 08:23:08 CDT 2009
The following issue has been RESOLVED.
======================================================================
http://bugs.digium.com/view.php?id=14945
======================================================================
Reported By: davidw
Assigned To: file
======================================================================
Project: Asterisk
Issue ID: 14945
Category: General
Reproducibility: sometimes
Severity: crash
Priority: normal
Status: resolved
Asterisk Version: 1.6.0.6
Regression: No
SVN Branch (only for SVN checkouts, not tarball releases): N/A
SVN Revision (number only!):
Request Review:
Resolution: fixed
Fixed in Version:
======================================================================
Date Submitted: 2009-04-21 11:44 CDT
Last Modified: 2009-04-27 08:23 CDT
======================================================================
Summary: Abort in free() in local_hangup, possibly related to
failure to provide ringback indication
Description:
We tried running under valgrind, but that didn't produce any obvious
indications of problems, and also made the ring back indication problem go
away, suggesting that there may be a common race condition that is causing
both.
I ran SIP history on the outgoing call and got the expected
INVITE/Trying/Ringing sequence.
gdb was only able to see the one thread. I don't know if that is because
it was an abort(), or because memory corruption has prevented it from
finding the information about the threads.
======================================================================
----------------------------------------------------------------------
(0103791) file (administrator) - 2009-04-27 08:23
http://bugs.digium.com/view.php?id=14945#c103791
----------------------------------------------------------------------
After looking at this further I believe my original change that I put in
also solved this issue. I let tests run for a day and previously I could
see in valgrind the issue happening, but now can not after I fixed the
issue.
Issue History
Date Modified Username Field Change
======================================================================
2009-04-27 08:23 file Note Added: 0103791
2009-04-27 08:23 file Status feedback => resolved
2009-04-27 08:23 file Resolution open => fixed
======================================================================
More information about the asterisk-bugs
mailing list