[Home]

Summary:ASTERISK-17371: Segmentation fault in __ast_module_user_remove ()
Reporter:David Brillert (aragon)Labels:
Date Opened:2011-02-09 08:59:11.000-0600Date Closed:2011-06-07 14:00:58
Priority:CriticalRegression?No
Status:Closed/CompleteComponents:Applications/app_dial
Versions:Frequency of
Occurrence
Related
Issues:
Environment:Attachments:( 0) feb_8_2011_bt_bt_full_thread_apply_all_bt_full.txt
Description:Random crashing in Asterisk 1.4 SVN r306120
I put this SVN release into production to solve segfault issues with call parking.


****** ADDITIONAL INFORMATION ******

Crashes are almost daily or multiple crashes per day; highly unstable.
Non-optimized gdb backtrace attached
Comments:By: David Brillert (aragon) 2011-03-10 15:50:55.000-0600

I have had to downgrade all Asterisk deployments because of this issue.
Now I am forced to use 1.4.39-1
Any chance of some feedback from a developer?

By: Russell Bryant (russell) 2011-03-14 11:23:15

Your backtrace appears to contain memory corruption and we require valgrind output in order to move this issue forward.

Please see https://wiki.asterisk.org/wiki/display/AST/Valgrind for more information about how to produce debugging information. Thanks!

By: David Brillert (aragon) 2011-03-14 12:11:56

Oh crap!

I don't know how to reproduce the problem to create the valgrind dump.
And this is a production system so I cannot run all day in valgrind waiting for the crash.

This will be nearly impossible to reproduce and create the required valgrind output so you might as well close this ticket.

By: Paul Belanger (pabelanger) 2011-04-25 22:08:14

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