[asterisk-bugs] [JIRA] (ASTERISK-28156) Race condition involving session->media (res_pjsip_session) leads to crash.

[Asterisk Team (JIRA)]

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

Asterisk Team commented on ASTERISK-28156:
------------------------------------------

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].

> Race condition involving session->media (res_pjsip_session) leads to crash.
> ---------------------------------------------------------------------------
>
>                 Key: ASTERISK-28156
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-28156
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Channels/chan_pjsip, Core/Bridging
>    Affects Versions: 13.20.0
>            Reporter: Paulo Vicentini
>              Labels: pjsip
>
> We are experiencing a crash due to a misuse of session->media container between threads running (bridge_channel_ind_thread / pbx_thread) (at t38_framehook_read function) and the thread running ast_taskprocessor_execute (res/res_pjsip_session.c:session_end)
> Depending on the SIP flow (during a disconnection) and the threads' code path, the session->media container is being destroyed (and set to NULL) by the thread running ast_taskprocessor_execute while the thread running t38_framehook_read is still referring to it.



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