[asterisk-bugs] [JIRA] (ASTERISK-27170) memory corruption probably related to operations involved into PickupChan
nappsoft (JIRA)
noreply at issues.asterisk.org
Wed Aug 23 03:32:08 CDT 2017
[ https://issues.asterisk.org/jira/browse/ASTERISK-27170?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=238177#comment-238177 ]
nappsoft commented on ASTERISK-27170:
-------------------------------------
Yesterday and today we have observed two more crashed in the live system, in both cases it happened again immediately after the call in which a PickupChan operation was involved had been hung up. => So this simply can't be a coincidence anymore. A pickup was involved into all observed crashes (7 during the last 16 days) since we started taking sip traces and as these operations happen in less than 1% of the calls (according to the number of calls per day and the pickups visible in the sip traces) it must have something to do with this operation...
> memory corruption probably related to operations involved into PickupChan
> -------------------------------------------------------------------------
>
> Key: ASTERISK-27170
> URL: https://issues.asterisk.org/jira/browse/ASTERISK-27170
> Project: Asterisk
> Issue Type: Bug
> Security Level: None
> Components: PBX/General
> Affects Versions: 13.16.0, 13.17.0
> Environment: 64bit linux musl 1.1.16-git
> Reporter: nappsoft
> Assignee: Unassigned
> Attachments: backtrace4.txt, crashlog.txt, trace_cel_crash.txt, trace.txt, valgrind2.txt, valgrind4.txt
>
>
> From time to time asterisk crashes when a component is trying to allocate memory. According to the sip traces this seem to happen mainly soon (sometimes some milliseconds, sometimes a few seconds) after a call in which a PickupChan operation was involved has been finished.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
More information about the asterisk-bugs
mailing list