[asterisk-bugs] [JIRA] Commented: (ASTERISK-20395) CLI Originate to chan_gtalk causes memory corruption crash

[Walter Doekes (JIRA)]

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

Walter Doekes commented on ASTERISK-20395:
------------------------------------------

Google says your valgrind is a bit old.
https://bugzilla.redhat.com/show_bug.cgi?id=626470

It might help if you update valgrind and get cleaner output.

> CLI Originate to chan_gtalk causes memory corruption crash
> ----------------------------------------------------------
>
>                 Key: ASTERISK-20395
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-20395
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Channels/chan_gtalk
>    Affects Versions: 1.8.15.1
>         Environment: centos 6.3
>            Reporter: Private Name
>            Assignee: Private Name
>         Attachments: crash-10.txt, crash-1.txt, crash-2.txt, crash-3.txt, crash-4.txt, crash-5.txt, Untitled 5.txt, valgrind.txt
>
>
> It crashes every few minutes. I am uploading the trace.
> I originate calls from the cli with originate and then if answered it gets dropped on a context with music-on-hold. No more logic to it.
> It uses jabber and gtalk

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira