[asterisk-bugs] [JIRA] (ASTERISK-24669) crash - memory corruption, or invalid channel snapshot in a stasis message

[Corey Farrell (JIRA)]

     [ https://issues.asterisk.org/jira/browse/ASTERISK-24669?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Corey Farrell closed ASTERISK-24669.
------------------------------------

    Resolution: Suspended

No response from reporter and inadequate information to determine a cause.  Lots has changed since Asterisk 13.1.0 so it's very possible this issue has been resolved.

If this is still an issue we will need a backtrace optimizations disabled against a newer release of Asterisk (13.19.1 is the current version right now).

> crash - memory corruption, or invalid channel snapshot in a stasis message
> --------------------------------------------------------------------------
>
>                 Key: ASTERISK-24669
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-24669
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Resources/res_stasis
>    Affects Versions: 13.1.0
>         Environment: 3.13.0-24-generic #46-Ubuntu SMP Thu Apr 10 19:11:08 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux
>            Reporter: Gregory Malsack
>         Attachments: backtrace.txt, valgrind_debug.txt
>
>
> <gmalsack> has anyone seen this issue on *13.1.0 http://pastebin.com/5zAdK6Fi - tail of full log here.... http://pastebin.com/58dj4ANB
> <gmalsack> 3.13.0-24-generic #46-Ubuntu SMP Thu Apr 10 19:11:08 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux
> <mjordan> ...
> <mjordan> get a full backtrace
> <gmalsack> seems to be causing the ast binary to crash, even with safe_asterisk running the service dies and has to be manually restarted.
> <mjordan> it's an abort, so yes
> <mjordan> you'll need to get a full backtrace.
> <gmalsack> ok, working on that now.
> <gmalsack> Full backtrace -> http://pastebin.com/NQVr9ZUN
> <mjordan> gmalsack: well, that's not good. That looks like a memory corruption, or invalid channel snapshot in a stasis message (which also shouldn't happen). You may need to run that under valgrind, but regardless, it is a bug
> Here's the valgrind.log file for review...
> [Edit by Rusty- Removed as per issue tracker guidelines... ]



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