[asterisk-bugs] [JIRA] (ASTERISK-30244) Crash in res_pjsip.so with TCP or TLS transports and Subscriptions

[Joshua C. Colp (JIRA)]

    [ https://issues.asterisk.org/jira/browse/ASTERISK-30244?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=260302#comment-260302 ] 

Joshua C. Colp commented on ASTERISK-30244:
-------------------------------------------

Not unregistering the monitor will result in a slow memory leak.

I think the underlying issue here is that the transport has gone away, but pubsub still has a pointer to it but no reference. It probably should have been terminated when the transport went away, and not later when the transport is no longer valid.

> Crash in res_pjsip.so with TCP or TLS transports and Subscriptions
> ------------------------------------------------------------------
>
>                 Key: ASTERISK-30244
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-30244
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Resources/res_pjsip_pubsub
>    Affects Versions: 18.14.0
>            Reporter: nappsoft
>            Severity: Major
>         Attachments: crash.txt
>
>
> We are observing crashes from time to time on less than one percent of systems. The segfault always happens at the same address in res_pjsip.so
> What they have in common: while we use lots of clients with TCP and TLS connections, only on these systems we have phones (Yealink) connected which subscribe over TLS and/or TCP.
> I can reproduce the crash from time to time when rebooting the phone. The crash happens as soon as it is up again and renewing the subscriptions.
> I was now able to create a backtrace, which you will find attached. 



--
This message was sent by Atlassian JIRA
(v6.2#6252)