| Summary: | ASTERISK-27645: Asterisk 13.18 crash in pj_atomic_dec_and_get | ||
| Reporter: | Jan Rozhon (loki) | Labels: | |
| Date Opened: | 2018-01-31 06:59:04.000-0600 | Date Closed: | 2018-02-12 10:26:26.000-0600 |
| Priority: | Major | Regression? | |
| Status: | Closed/Complete | Components: | pjproject/pjsip |
| Versions: | 13.18.0 | Frequency of Occurrence | One Time |
| Related Issues: | |||
| Environment: | centos 6/ FreePBX distro 10.13.66-22 | Attachments: | ( 0) backtrace.txt |
| Description: | Asterisk crashed with core dumped. I am not sure, what caused the problem, it is the first time I have encountered this issue/backtrace.
Link to backtrace: http://pastebin.freepbx.org/view/df16f304 Attached the backtrace to the issue as [^backtrace.txt] | ||
| Comments: | By: Asterisk Team (asteriskteam) 2018-01-31 06:59:04.785-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. 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: George Joseph (gjoseph) 2018-02-08 13:20:03.108-0600 It looks like there was some memory corruption. Can you recompile with MALLOC_DEBUG along with DONT_OPTIMIZE and BETTER_BACKTRACES? There should be little performance impact on a production system. By: Jan Rozhon (loki) 2018-02-12 09:58:12.718-0600 George, unfortunately that is not an option for me, since I rely heavily on the FreePBX packaging. What I can do is run a clone system and simulate traffic on it. But I do not have a slightest clue on what to simulate (load, message format, simultaneous events...). Thank you, Jan By: George Joseph (gjoseph) 2018-02-12 10:26:04.339-0600 Well, since this was a one-time crash, I'm going to close the issue for now. If it happens again, get the full backtrace info by following the instructions on the Asterisk wiki[1] and re-open the issue. [1]: https://wiki.asterisk.org/wiki/display/AST/Getting+a+Backtrace | ||