| Summary: | ASTERISK-30498: Segfault / 16.22.0 | ||||
| Reporter: | Nicholas Carr (connectsmart) | Labels: | |||
| Date Opened: | 2023-04-20 01:14:48 | Date Closed: | 2023-04-20 04:35:24 | ||
| Priority: | Critical | Regression? | |||
| Status: | Closed/Complete | Components: | pjproject/pjsip | ||
| Versions: | 16.22.0 | Frequency of Occurrence | Occasional | ||
| Related Issues: |
| ||||
| Environment: | MS Azure, CentOS 7.9, 2 vCPU, 8GB RAM | Attachments: | ( 0) 2023-04-16T23-27-15+0000-brief.txt ( 1) 2023-04-16T23-27-15+0000-full.txt ( 2) 2023-04-16T23-27-15+0000-info.txt ( 3) 2023-04-16T23-27-15+0000-locks.txt ( 4) 2023-04-16T23-27-15+0000-thread1.txt ( 5) 2023-04-16T23-58-35+0000-brief.txt ( 6) 2023-04-16T23-58-35+0000-full.txt ( 7) 2023-04-16T23-58-35+0000-info.txt ( 8) 2023-04-16T23-58-35+0000-locks.txt ( 9) 2023-04-16T23-58-35+0000-thread1.txt (10) 2023-04-17T06-36-52+0000-brief.txt (11) 2023-04-17T06-36-52+0000-full.txt (12) 2023-04-17T06-36-52+0000-info.txt (13) 2023-04-17T06-36-52+0000-locks.txt (14) 2023-04-17T06-36-52+0000-thread1.txt (15) 2023-04-19T06-33-42+0000-brief.txt (16) 2023-04-19T06-33-42+0000-full.txt (17) 2023-04-19T06-33-42+0000-info.txt (18) 2023-04-19T06-33-42+0000-locks.txt (19) 2023-04-19T06-33-42+0000-thread1.txt | ||
| Description: | We have had 4 crashes occur in the last 3 days.
As far as we can tell they all look to be related to a lock acquire or lock release during a registration request. | ||||
| Comments: | By: Asterisk Team (asteriskteam) 2023-04-20 01:14:50.645-0500 WARNING JIRA will be going read-only at the end of April, 2023. We will be starting fresh on Github at https://github.com/asterisk/asterisk at that time. No issues or patches will be copied to Github. If you file an issue on JIRA at this time you will need to recreate it on Github after this date. The same applies if you have a patch. WARNING 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: Nicholas Carr (connectsmart) 2023-04-20 01:18:37.285-0500 Exports by ast_coredumper | ||||