Summary:	ASTERISK-25344: Random crashes (SIGSEGV / SIGABRT) on Asterisk 13.1.0~dfsg-1+b1 (possibly in combination with stasis)
Reporter:	Mauro Guadagnini (mauro.guadagnini)	Labels:
Date Opened:	2015-08-25 09:30:22	Date Closed:	2015-08-31 09:18:36
Priority:	Major	Regression?	No
Status:	Closed/Complete	Components:	.Release/Targets
Versions:	13.1.0	Frequency of Occurrence	Frequent
Related Issues:
Environment:	/etc/debian_version: stretch/sid Linux 4.1.0-1-amd64 #1 SMP Debian 4.1.3-1 (2015-08-03) x86_64 GNU/Linux Asterisk package version: 1:13.1.0~dfsg-1.1 (amd64)	Attachments:	( 0) backtrace_20150825_112317.txt ( 1) backtrace_20150825_140557.txt ( 2) backtrace_20150825_151612.txt ( 3) dmesg_output.txt ( 4) full_logfile.txt
Description:	Hello, We have a custom call-center-web-application based on PHP and JS, which tracks events using websockets. The application works, but we are experiencing random crashes with Asterisk. The crashes are occurring at mostly random times (almost all during work time), here are the times when Asterisk is starting up after the crash: 24. Aug 2015: 06:25, 12:29, 14:07, 15:14, 15:54, 17:08 25. Aug 2015: 11:12, 11:23 (backtrace_20150825_112317.txt attached), 12:23, 13:36, 14:05 (backtrace_20150825_140557.txt attached), 15:16 (backtrace_20150825_151612.txt attached) Additionaly, I have attached the output of dmesg -T relating to Asterisk in dmesg_output.txt and the full log (full_logfile.txt) including the following message types: notice,warning,error,debug,verbose,dtmf,fax. If you require any further information, feel free to contact me. Thank you for your help in this matter.
Comments:	By: Asterisk Team (asteriskteam) 2015-08-25 09:30:24.275-0500 Thanks for creating a report! The issue has entered the triage process. That means the issue will wait in this status until a Bug Marshal has an opportunity to review the issue. Once the issue has been reviewed you will receive comments regarding the next steps towards resolution. A good first step is for you to review the [Asterisk Issue Guidelines|https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines] if you haven't already. The guidelines detail what is expected from an Asterisk issue report. Then, if you are submitting a patch, please review the [Patch Contribution Process|https://wiki.asterisk.org/wiki/display/AST/Patch+Contribution+Process]. By: Rusty Newton (rnewton) 2015-08-26 15:28:49.564-0500 Be sure to collect some backtraces following the instructions here: https://wiki.asterisk.org/wiki/display/AST/Getting+a+Backtrace That is, be sure you compile with BETTER_BACKTRACES and DONT_OPTIMIZE. I see a lot of optimizations in your traces. Please also test with the latest source release or Git branch head to compare. Based on your traces you will also want to collect valgrind or malloc_debug output: https://wiki.asterisk.org/wiki/display/AST/MALLOC_DEBUG+Compiler+Flag By: Mauro Guadagnini (mauro.guadagnini) 2015-08-27 03:14:26.059-0500 Thank you for your answer. I compiled the latest version (13.5.0) with BETTER_BACKTRACES and DONT_OPTIMIZE. We observe that the crashes happen less often when there are less people using Asterisk. I will post the new backtraces as soon as we experience the next crash. EDIT: instead of MALLOC_DEBUG we will use valgrind. I will send its output then as well. By: Rusty Newton (rnewton) 2015-08-28 08:53:45.695-0500 Thanks Mauro! By: Mauro Guadagnini (mauro.guadagnini) 2015-08-31 01:42:17.170-0500 We haven't experienced a crash since the installation of the latest version. I think that the problem doesn't exist anymore with version 13.5.0. Thank you very much for your help. By: Rusty Newton (rnewton) 2015-08-31 09:18:36.302-0500 That is good to hear. If you do run into another crash in the latest version please open a new issue with all the required debug. Thanks!