[Home]

Summary:ASTERISK-28438: chan_pjsip: segfault in pj_grp_lock_acquire
Reporter:Andrew Yager (andrewyager)Labels:pjsip
Date Opened:2019-06-06 05:06:22Date Closed:2019-06-20 12:00:02
Priority:MajorRegression?
Status:Closed/CompleteComponents:pjproject/pjsip
Versions:15.7.1 Frequency of
Occurrence
Occasional
Related
Issues:
Environment:Linux host 4.4.0-148-generic #174-Ubuntu SMP Tue May 7 12:20:14 UTC 2019 x86_64 x86_64 x86_64 GNU/LinuxAttachments:( 0) core-brief.txt
( 1) core-full.txt
( 2) core-locks.txt
( 3) core-thread1.txt
Description:Infrequent segfault from within chan_pjsip while processing message. Backtraces attached
Comments:By: Asterisk Team (asteriskteam) 2019-06-06 05:06:23.151-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: Andrew Yager (andrewyager) 2019-06-06 05:06:51.156-0500

backtraces

By: Joshua C. Colp (jcolp) 2019-06-06 05:09:36.753-0500

Per the Asterisk versions page [1], the maintenance (bug fix) support for the Asterisk branch you are using has ended. For continued maintenance support please move to a supported branch of Asterisk. After testing with a supported branch, if you find this problem has not been resolved, please open a new issue against the latest version of that Asterisk branch.

Thanks!

[1] https://wiki.asterisk.org/wiki/display/AST/Asterisk+Versions



By: Joshua C. Colp (jcolp) 2019-06-06 05:10:12.428-0500

In particular Teluu (maker of PJSIP) has done work in this area and we have pulled those changes into supported branches.

By: Andrew Yager (andrewyager) 2019-06-06 05:14:24.631-0500

Thanks. Will upgrade to 16.4 release series and test.

By: Asterisk Team (asteriskteam) 2019-06-20 12:00:02.079-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