[Home]

Summary:ASTERISK-28410: Crash on unload res_pjsip_mwi.so and show subscriptions
Reporter:Joshua Elson (joshelson)Labels:pjsip
Date Opened:2019-05-08 16:24:48Date Closed:
Priority:MinorRegression?
Status:Open/NewComponents:Resources/res_pjsip_mwi
Versions:16.3.0 Frequency of
Occurrence
Related
Issues:
Environment:Attachments:( 0) core.den-media-9.fluentcloud.com-2019-05-08T14-05-46-0600-brief.txt
( 1) core.den-media-9.fluentcloud.com-2019-05-08T14-05-46-0600-full.txt
( 2) core.den-media-9.fluentcloud.com-2019-05-08T14-05-46-0600-locks.txt
( 3) core.den-media-9.fluentcloud.com-2019-05-08T14-05-46-0600-thread1.txt
Description:We have a crash that isn't totally reproducible quite yet but happened on the invocation of module load res_pjsip_mwi.so on a running 16.3.0 system.
Comments:By: Asterisk Team (asteriskteam) 2019-05-08 16:24:48.781-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: Joshua Elson (joshelson) 2019-05-08 16:25:30.198-0500

Backtrace attached.
By: George Joseph (gjoseph) 2019-05-09 08:17:25.226-0500

This is weird.  The backtrace shows a segfault but  looks like it's in cli_show_subscriptions_inbound.  I.E.  It crashed when someone did a "pjsip show subscriptions inbound" from the CLI.

Can you reproduce this at all?
By: Joshua Elson (joshelson) 2019-05-09 12:08:03.414-0500

We got a repro.

Unload res_pjsip_mwi.so.

Then list subscriptions from the CLI. It will crash 100% of the time.
By: George Joseph (gjoseph) 2019-05-09 12:41:56.559-0500

Oh my.  Yes it does. :(