[asterisk-bugs] [JIRA] (ASTERISK-28885) res_rtp_asterisk.c: ast_rtp_remote_address_set SIGABRT

[Asterisk Team (JIRA)]

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

Asterisk Team commented on ASTERISK-28885:
------------------------------------------

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.

> res_rtp_asterisk.c: ast_rtp_remote_address_set SIGABRT
> ------------------------------------------------------
>
>                 Key: ASTERISK-28885
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-28885
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Resources/res_rtp_asterisk
>    Affects Versions: 13.32.0
>         Environment: Centos 7.5, Asterisk 13.32.0
>            Reporter: Josep B
>              Labels: webrtc
>
> Hi,
> We are using asterisk 13.32.0 with pjsip 2.9 bundled, using webrtc transport with ‘rel100‘ activated.
> We get a SIGABRT crash:
> #0  0x00007ff76c375337 in raise () from /usr/lib64/libc.so.6
> #1  0x00007ff76c376a28 in abort () from /usr/lib64/libc.so.6
> #2  0x00007ff76c3b7e87 in __libc_message () from /usr/lib64/libc.so.6
> #3  0x00007ff76c3c0679 in _int_free () from /usr/lib64/libc.so.6
> #4  0x00007ff69acd67e7 in ast_rtp_remote_address_set (instance=<optimized out>, addr=0x7ff68818e320) at res_rtp_asterisk.c:6159
> #5  0x0000000000590655 in rtp_instance_set_incoming_source_address_nolock (address=0x7ff68ce97b80, instance=0x7ff68818e1e8) at rtp_engine.c:549
> #6  ast_rtp_instance_set_requested_target_address (instance=instance at entry=0x7ff68818e1e8, address=address at entry=0x7ff68ce97b80) at rtp_engine.c:569
> #7  0x00007ff69acdc4fc in ast_rtp_ice_start_media (status=<optimized out>, ice=0x7ff68801e9c8) at res_rtp_asterisk.c:2172
> #8  ast_rtp_on_ice_complete (ice=0x7ff68801e9c8, status=<optimized out>) at res_rtp_asterisk.c:2217
> #9  0x00007ff76efe9eb5 in on_timer (th=<optimized out>, te=<optimized out>) at ../src/pjnath/ice_session.c:1177
> #10 0x00007ff76f065147 in pj_timer_heap_poll (ht=0x4ba32b8, next_delay=next_delay at entry=0x0) at ../src/pj/timer.c:659
> #11 0x00007ff69acd5420 in timer_worker_thread (data=<optimized out>) at res_rtp_asterisk.c:2296
> #12 0x00007ff76f04e1a0 in thread_main (param=0x5faac00) at ../src/pj/os_core_unix.c:541
> #13 0x00007ff76d09be65 in start_thread () from /usr/lib64/libpthread.so.0
> #14 0x00007ff76c43d88d in clone () from /usr/lib64/libc.so.6
> Related code lines (res_rtp_asterisk.c:6159) is: ast_free(rtp->rtcp->local_addr_str);
> Seems like rtp->rtcp->local_addr_str memory was corrupt (released, allocated or wrote) and libc asserts it.
> We attach additional information.
> ¿Does anyone know if it’s a known issue?
> We can colaborate testing or getting additional information.



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