| Summary: | ASTERISK-29092: Asterisk crashes because of segfault | ||
| Reporter: | Alex Badalien (badalien) | Labels: | |
| Date Opened: | 2020-09-23 06:29:29 | Date Closed: | 2020-10-07 12:00:01 |
| Priority: | Critical | Regression? | No |
| Status: | Closed/Complete | Components: | Channels/chan_sip/General |
| Versions: | 16.11.1 | Frequency of Occurrence | Occasional |
| Related Issues: | |||
| Environment: | OS : Ubuntu 18.04.4 LTS CPU : Intel(R) Xeon(R) CPU E3-1270 v6 @ 3.80GHz RAM : 16GiB DIMM DDR4 Synchronous 2667 MHz (0.4 ns) | Attachments: | |
| Description: | Asterisk crashes due to a segmentation fault when trying to access the same memory segment
Checking the state of RAM on the server did not reveal any problems | ||
| Comments: | By: Asterisk Team (asteriskteam) 2020-09-23 06:29:30.821-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. 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: Joshua C. Colp (jcolp) 2020-09-23 06:38:35.067-0500 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 As well your version of Asterisk is old, upgrading to the latest is recommended. The chan_sip module, if that is the source, is also community supported so if there is a problem with it there is no guarantee on when or if it will be resolved. By: Asterisk Team (asteriskteam) 2020-10-07 12:00:00.894-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 | ||