| Summary: | ASTERISK-28490: Segfault in chan_pjsip in grp_lock_dec_ref | ||||
| Reporter: | Ross Beer (rossbeer) | Labels: | pjsip | ||
| Date Opened: | 2019-07-31 05:59:35 | Date Closed: | 2019-08-01 09:39:37 | ||
| Priority: | Major | Regression? | No | ||
| Status: | Closed/Complete | Components: | Resources/res_pjsip | ||
| Versions: | 13.28.0 GIT | Frequency of Occurrence | Occasional | ||
| Related Issues: |
| ||||
| Environment: | Cent OS 7 | Attachments: | ( 0) core-asterisk-145834-pbx-1564569425-thread1.txt | ||
| Description: | Asterisk segfaults when decrementing the log reference:
{noformat} #0 0x00007f35a02a61e1 in grp_lock_dec_ref (glock=0x111) at ../src/pj/lock.c:554 cnt = 0 #1 0x00007f35a02a6242 in pj_grp_lock_dec_ref (glock=0x111) at ../src/pj/lock.c:646 {noformat} | ||||
| Comments: | By: Asterisk Team (asteriskteam) 2019-07-31 05:59:36.494-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: Benjamin Keith Ford (bford) 2019-07-31 12:54:02.210-0500 This looks like it may be an issue within pjproject, as this thread doesn't appear to correlate to any Asterisk functions. Can you provide some context as to what is happening at the time of the crash? I see that the frequency is also "Occasional" - if you do know how to replicate this, how reliable is it? By: Ross Beer (rossbeer) 2019-08-01 02:43:40.180-0500 I have raised the issue to the pjproject team for further investigation. I have full backtraces with binaries if that would help? By: Benjamin Keith Ford (bford) 2019-08-01 09:38:33.737-0500 If you can attach all that information to ASTERISK-28161, that would be great. We think this is the same underlying issue. I'm going to close this one and all other updates can be done on 28161. | ||||