Summary: | ASTERISK-29153: __pthread_mutex_lock(): asterisk killed by SIGSEGV | ||
Reporter: | Mark Petersen (roadkill) | Labels: | |
Date Opened: | 2020-11-11 04:20:16.000-0600 | Date Closed: | 2020-11-11 07:28:11.000-0600 |
Priority: | Minor | Regression? | No |
Status: | Closed/Complete | Components: | Core/Dial pjproject/pjsip |
Versions: | 18.0.1 | Frequency of Occurrence | Constant |
Related Issues: | |||
Environment: | CentOS Linux release 8.2.2004 (Core) | Attachments: | ( 0) asterisk.conf ( 1) coredump-brief.txt ( 2) coredump-full.txt ( 3) coredump-info.txt ( 4) coredump-locks.txt ( 5) coredump-thread1.txt ( 6) extensions.conf ( 7) modules.conf ( 8) pjsip_wizard.conf ( 9) pjsip.conf |
Description: | running a load test with 10call/sec
is failing after 100 calls | ||
Comments: | By: Asterisk Team (asteriskteam) 2020-11-11 04:20:16.764-0600 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. Please note that log messages and other files should not be sent to the Sangoma Asterisk Team unless explicitly asked for. All files should be placed on this issue in a sanitized fashion as needed. 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. Please note that by submitting data, code, or documentation to Sangoma through JIRA, you accept the Terms of Use present at [https://www.asterisk.org/terms-of-use/|https://www.asterisk.org/terms-of-use/]. By: Mark Petersen (roadkill) 2020-11-11 04:21:47.122-0600 running a loadtest with sipp 10 call per sec will die after 200 calls server x.101 (asterisk 18.0.1) context with only a Dial(PJSIP/service@SIPP3) server x.103 (sipp reciver) sipp -sn uas -bind_local 10.253.253.103 server x.104: (sipp sender) sipp -sn uac 10.253.253.101 -i 10.253.253.104 -r 10 -d 1000 -m 20000 By: Joshua C. Colp (jcolp) 2020-11-11 04:23:12.208-0600 Thank you for the crash report. However, we need more information to investigate the crash. Please provide: 1. A backtrace generated from a core dump using the instructions provided on the Asterisk wiki [1]. 2. Specific steps taken that lead to the crash. 3. All configuration information necesary to reproduce the crash. Thanks! [1]: https://wiki.asterisk.org/wiki/display/AST/Getting+a+Backtrace By: Mark Petersen (roadkill) 2020-11-11 04:24:37.620-0600 ast_coredumper By: Joshua C. Colp (jcolp) 2020-11-11 04:31:06.546-0600 What flags and options in menuselect were used for building Asterisk? Do you have MALLOC_DEBUG enabled? By: Joshua C. Colp (jcolp) 2020-11-11 04:33:26.139-0600 Do you have DEBUG_THREADS enabled? By: Mark Petersen (roadkill) 2020-11-11 04:35:45.717-0600 [*] DONT_OPTIMIZE [ ] COMPILE_DOUBLE [*] DEBUG_THREADS [*] DEBUG_FD_LEAKS [*] BETTER_BACKTRACES [ ] LOTS_OF_SPANS [*] MALLOC_DEBUG [ ] DEBUG_CHAOS [ ] BUILD_NATIVE [*] OPTIONAL_API By: Joshua C. Colp (jcolp) 2020-11-11 04:42:03.726-0600 Unless you are debugging a specific issue then running with DEBUG_THREADS and MALLOC_DEBUG is NOT recommended. It has serious performance consequences and drastically changes the code execution. Does the problem exist without having them enabled? By: Mark Petersen (roadkill) 2020-11-11 04:48:45.104-0600 original it was compiled without any options and I experienced problems with the load test will test with only DONT_OPTIMIZE By: Mark Petersen (roadkill) 2020-11-11 07:21:24.188-0600 have now tried without DEBUG_THREADS and MALLOC_DEBUG and I no long experience any crashed but I do see other issues, but that it for a different ticket PLEASE CLOSE |