[asterisk-bugs] [JIRA] (ASTERISK-28941) segfault in pjsip timer

[Alan Graham (JIRA)]

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

Alan Graham edited comment on ASTERISK-28941 at 6/23/20 9:39 AM:
-----------------------------------------------------------------

We've been running this in production for a full week now and we've yet to see any new incidences of the timer segv, when typically we'd see it a couple-three times a week, easily. This is an ARI-only environment in k8s, so that's the extent to which we've been able to test it. We've closed our internal ticket for it so we're satisfied that this is fixed.


was (Author: zerohalo):
We've been running this in production for a full week now and we've yet to see any new incidences of the timer segv, when typically we'd see it a couple-three times a week, easily. This is an ARI-only environment in k8s, so that's the extent to which we've been able to test it.

> segfault in pjsip timer
> -----------------------
>
>                 Key: ASTERISK-28941
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-28941
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: pjproject/pjsip
>    Affects Versions: 16.8.0, 16.9.0, 16.10.0
>         Environment: Debian Stretch
>            Reporter: Alan Graham
>            Assignee: Unassigned
>
> At least daily, sometimes multiple times daily, Asterisk crashes in this thread:
> {noformat}
> Thread 1 (Thread 0x7f9f6e98b700 (LWP 53)):
> #0  0x00007f9fdc30f711 in copy_node (ht=0x561e6933d960, slot=0, moved_node=0x7f9fb006b0f0) at ../src/pj/timer.c:137
> #1  0x00007f9fdc30f9ee in reheap_down (ht=0x561e6933d960, moved_node=0x7f9fd009c680, slot=0, child=1) at ../src/pj/timer.c:185
> #2  0x00007f9fdc30fd34 in remove_node (ht=0x561e6933d960, slot=0) at ../src/pj/timer.c:252
> #3  0x00007f9fdc310694 in pj_timer_heap_poll (ht=0x561e6933d960, next_delay=0x7f9f6e98ae10) at ../src/pj/timer.c:643
> #4  0x00007f9fdc259c3e in pjsip_endpt_handle_events2 (endpt=0x561e6933d678, max_timeout=0x7f9f6e98ae80, p_count=0x0) at ../src/pjsip/sip_endpoint.c:716
> #5  0x00007f9fdc259d84 in pjsip_endpt_handle_events (endpt=0x561e6933d678, max_timeout=0x7f9f6e98ae80) at ../src/pjsip/sip_endpoint.c:777
> #6  0x00007f9f91580936 in monitor_thread_exec (endpt=0x0) at res_pjsip.c:4715
> #7  0x00007f9fdc2f71d4 in thread_main (param=0x561e69569b68) at ../src/pj/os_core_unix.c:541
> #8  0x00007f9fda7854a4 in start_thread (arg=0x7f9f6e98b700) at pthread_create.c:456
> #9  0x00007f9fd938fd0f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:97
> {noformat}
> It looks similar to older issues like ASTERISK-27187, though that issue used external pjsip and we're using bundled.
> I have complete core and BT available, if needed.



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