Summary:	ASTERISK-27150: Periodic crash in ast_channel_snapshot_create
Reporter:	Leandro Dardini (ldardini)	Labels:
Date Opened:	2017-07-22 11:28:37	Date Closed:	2020-01-14 11:13:54.000-0600
Priority:	Major	Regression?
Status:	Closed/Complete	Components:
Versions:	13.17.0	Frequency of Occurrence	Frequent
Related Issues:
Environment:	CentOS 6.9 64 bit, ODBC 2.3.4-1, chan_sip with no MWI subscribe	Attachments:	( 0) core.Q01PBX001-2017-07-20T15-56-30+0200-brief.txt ( 1) core.Q01PBX001-2017-07-20T15-56-30+0200-full.txt ( 2) core.Q01PBX001-2017-07-20T15-56-30+0200-locks.txt ( 3) core.Q01PBX001-2017-07-20T15-56-30+0200-thread1.txt ( 4) jira_asterisk_27150_v13_valgrind_fixes.patch ( 5) valgrind.txt
Description:	Asterisk process is experiencing crash every few other days with segmentation fault message during normal operation.
Comments:	By: Asterisk Team (asteriskteam) 2017-07-22 11:28:37.779-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: Leandro Dardini (ldardini) 2017-07-22 11:29:42.025-0500 ast_coredumper generated files By: Richard Mudgett (rmudgett) 2017-07-24 09:43:35.473-0500 Your backtrace appears to contain a memory corruption. We need one or both of the following items to continue investigation of the issue: 1. Valgrind output. See https://wiki.asterisk.org/wiki/display/AST/Valgrind for instructions on how to use Valgrind with Asterisk. 2. MALLOC_DEBUG output. See https://wiki.asterisk.org/wiki/display/AST/MALLOC_DEBUG+Compiler+Flag for instructions on how to use the MALLOC_DEBUG option. Note that MALLOC_DEBUG and Valgrind are mutually exclusive options. Valgrind output is preferable, but will be more system resource intensive and may be difficult to get on a production system. In such a case, you may have better luck getting the necessary output from MALLOC_DEBUG. By: nappsoft (nappsoft) 2017-07-25 09:22:39.842-0500 Just one question: do you have some mobile phone sip clients (for example zoiper) connected to your system that are not reachable from time to time? I'm asking as we currently experience memory corruption issues on one Asterisk 13.17 based system as well (segfault in malloc every second or third day). The strange thing is that we only have this issue on one single virtual machine while we run Asterisk on tons of VMs on the same hardware with almost the same configuration (we provision the config, so it only differs in usernames, passwords and such things) and soft- and hardphones from the same vendors. The only obvious difference is that some zoiper clients that are unreachable from time to time while the registration is still valid are connected to this system. By: Leandro Dardini (ldardini) 2017-07-26 17:59:36.149-0500 I have the valgrind result for two days of work, not at the usual level, but enough traffic to generate some result. I can't judge if interesting. By: Richard Mudgett (rmudgett) 2017-07-27 11:26:38.595-0500 Unfortunately, the problem doesn't appear to have happened under valgrind.  The valgrind output is only showing uses of uninitialized data by asterisk and other libraries; no invalid writes that would corrupt memory.  Valgrind either threw off the timing so the problem doesn't happen or what triggers the problem didn't happen. MALLOC_DEBUG may have better luck catching the problem. By: Asterisk Team (asteriskteam) 2017-08-10 12:00:02.320-0500 Suspended due to lack of activity. This issue will be automatically re-opened if the reporter posts a comment. If you are not the reporter and would like this re-opened please create a new issue instead. If the new issue is related to this one a link will be created during the triage process. Further information on issue tracker usage can be found in the Asterisk Issue Guidlines [1]. [1] https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines By: Richard Mudgett (rmudgett) 2017-08-10 14:19:18.249-0500 [^jira_asterisk_27150_v13_valgrind_fixes.patch] - This patch fixes some of the valgrind findings.  One of the findings does seem like it could corrupt memory.  However, I cannot say if it will fix your memory corruption problem.  I wanted to get some of the valgrind findings fixed before those findings get lost in the haystack of dead issues.