[Home]

Summary:ASTERISK-28594: Chan_SIP Crash (Segmentation fault)
Reporter:Neimar Avila (neimar.avila)Labels:
Date Opened:2019-10-20 10:13:34Date Closed:2019-11-05 12:00:01.000-0600
Priority:MajorRegression?
Status:Closed/CompleteComponents:Channels/chan_sip/General
Versions:16.6.1 Frequency of
Occurrence		Frequent
Related
Issues:
Environment:Centos 7 / Asterisk 16.6.1Attachments:( 0) core.pabx.vsphone.com.br-2019-10-20T11-55-51-0300-brief.txt
( 1) core.pabx.vsphone.com.br-2019-10-20T11-55-51-0300-full.txt
( 2) core.pabx.vsphone.com.br-2019-10-20T11-55-51-0300-locks.txt
( 3) core.pabx.vsphone.com.br-2019-10-20T11-55-51-0300-thread1.txt
Description:Asterisk Compiled with:
./configure --libdir=/usr/lib64 --with-jansson-bundled

modules.conf
noload => chan_alsa.so
noload => chan_console.so
noload => chan_mgcp.so
noload => chan_motif.so
noload => chan_oss.so
noload => chan_phone.so
noload => chan_skinny.so
noload => chan_unistim.so

noload => res_config_curl.so
noload => res_config_ldap.so
noload => res_config_odbc.so
noload => res_config_pgsql.so
noload => res_config_sqlite3.so
noload => res_config_sqlite.so
noload => res_hep_pjsip.so
noload => res_hep_rtcp.so
noload => res_hep.so

noload => cel_custom.so
noload => cel_manager.so
noload => cel_odbc.so
noload => cel_pgsql.so
noload => cel_sqlite3_custom.so
noload => cel_tds.so
noload => cel_radius.so

noload => cdr_custom.so
noload => cdr_csv.so
noload => cdr_sqlite3_custom.so
noload => cdr_radius.so
noload => cdr_manager.so
noload => cdr_pgsql.so
noload => cdr_tds.so
noload => cdr_odbc.so

extensions.conf
[public]
exten => 9000,1,MixMonitor(${UNIQUEID}.wav49)
same=> n,Dial(SIP/${EXTEN}@172.16.11.131)

172.16.11.131 is another Asterisk 16.6.1 -
sip.conf
allowguest=yes
context=public

[public]
exten=> 9000,1,Answer();
same=> n,MusicOnHold()


I'm using sipp:
sipp -s 9000 127.0.0.1:5062 -sf sipp_pcap.xml -i 127.0.0.1 -p 5090 -d 90000 -l 300
Comments:By: Asterisk Team (asteriskteam) 2019-10-20 10:13:35.767-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].

Please note that once your issue enters an open state it has been accepted. As Asterisk is an open source project there is no guarantee or timeframe on when your issue will be looked into. If you need expedient resolution you will need to find and pay a suitable developer. Asking for an update on your issue will not yield any progress on it and will not result in a response. All updates are posted to the issue when they occur.
By: Joshua C. Colp (jcolp) 2019-10-22 08:43:05.619-0500

You have MALLOC_DEBUG enabled which diminishes performance a ton. If you disable it, does that alter the result?

What other compiler flags do you have enabled in menuselect?
By: Richard Mudgett (rmudgett) 2019-10-22 08:54:48.042-0500

That's DEBUG_THREADS not MALLOC_DEBUG. :)
By: Neimar Avila (neimar.avila) 2019-10-22 08:58:23.527-0500

Hello, I will repeat the tests without debug MALLOC_DEBUG
Using:
DEBUG_THREADS
DEBUG_FD_LEAKS
BETTER_BACKTRACES      
By: Joshua C. Colp (jcolp) 2019-10-22 09:01:14.579-0500

Please don't enable any of those debug options.
By: Neimar Avila (neimar.avila) 2019-10-22 09:05:17.243-0500

OK, only de-select DONT_OPTIMIZE or don't change results?
By: Joshua C. Colp (jcolp) 2019-10-22 09:09:00.678-0500

You can leave DONT_OPTIMIZE enabled, but please do not enable MALLOC_DEBUG, DEBUG_THREADS, DEBUG_FD_LEAKS, and BETTER_BACKTRACES.

They are for debugging only when a problem is occurring.
By: Asterisk Team (asteriskteam) 2019-11-05 12:00:00.880-0600

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