| Summary: | ASTERISK-24669: crash - memory corruption, or invalid channel snapshot in a stasis message | ||
| Reporter: | Gregory Malsack (gmalsack) | Labels: | |
| Date Opened: | 2015-01-07 10:33:57.000-0600 | Date Closed: | 2018-02-20 04:55:34.000-0600 |
| Priority: | Major | Regression? | |
| Status: | Closed/Complete | Components: | Resources/res_stasis |
| Versions: | 13.1.0 | Frequency of Occurrence | Frequent |
| Related Issues: | |||
| 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 | Attachments: | ( 0) backtrace.txt ( 1) valgrind_debug.txt |
| Description: | <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... ] | ||
| Comments: | By: Rusty Newton (rnewton) 2015-01-08 08:31:20.478-0600 Removed debug from the *description* field and attaching as a .txt file as per the guildlines. Please check them out in the future [Asterisk Issue Guidelines|https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines] Thanks! :) By: Rusty Newton (rnewton) 2015-01-08 08:34:14.188-0600 Also, please don't link to external services for debug needed for the issue. Can you get another backtrace without optimizations (use DONT_OPTIMIZE and BETTER_BACKTRACES) and *attach* that to the issue? By: Rusty Newton (rnewton) 2015-01-08 08:36:05.980-0600 Press Send Back or Enter Feedback once you have gathered the additional info. By: Rusty Newton (rnewton) 2015-01-29 18:20:14.474-0600 Gregory hasn't responded. I'm attaching the trace that we do have (from Gregory's pastebin) By: Corey Farrell (coreyfarrell) 2018-02-20 04:55:35.129-0600 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). | ||