|Summary:||ASTERISK-18423: Crash in AMI initiated sip show peers|
|Reporter:||Matthew Livingstone (mlivingstone)||Labels:|
|Date Opened:||2011-09-06 12:54:44||Date Closed:||2012-04-24 14:43:15|
|Environment:||2.6.26-2-amd64 2.6.32-5-amd64 Debian 6.0.2 (squeeze)||Attachments:||( 0) bt-btfull.txt|
|Description:||One of our clients (also our largest) crashes regularly, and this is not the first time we've seen a crash on calling _sip_show_peers. We've tried just about everything we can think of, and the crashes continue.|
With DEBUG_THREADS enabled the system locks up, so unfortunately we can't get a back trace with debug.
Before or during each crash, the Recv-Q (visible via netstat -anp | grep 5060) is always full. Not sure if this is part of the issue, but there is definitely a correlation.
I will attach what we have for a back trace.
|Comments:||By: Gregory Hinton Nietsky (irroot) 2011-09-06 14:18:05.472-0500|
Its not easy to debug it from this libc seems optomised out. there is a crash in free this is odd.
By: Matthew Livingstone (mlivingstone) 2011-09-06 16:16:01.282-0500
We've got the DONT_OPTIMIZE flag set. Is there something else we can do to make the back trace easier to read?
Also, most of the crashes in the past have all happened in free for us too.
By: Richard Mudgett (rmudgett) 2011-09-06 17:18:17.582-0500
This is not really a crash but an abort likely because of an assertion failure in free() caused by a double free or other invalid memory pointer passed to free().
By: Leif Madsen (lmadsen) 2011-09-13 11:16:26.068-0500
What more information is required here then?
By: Matt Jordan (mjordan) 2012-03-23 14:44:55.870-0500
This appears to be related to ASTERISK-19231 and ASTERISK-19361, a fix for which should be in Asterisk 188.8.131.52 (currently in RC status). You may want to test with the most recent release candidate, or test with 184.108.40.206 when it is released.
By: Matt Jordan (mjordan) 2012-04-24 14:43:10.159-0500
Suspended due to lack of activity. Please request a bug marshal in #asterisk-bugs on the IRC network irc.freenode.net to reopen the issue should you have the additional information requested. Further information can be found at http://www.asterisk.org/developers/bug-guidelines