| Summary: | ASTERISK-21895: Aborted in ast_hangup -> __ast_manager_event_multichan -> append_event | ||||
| Reporter: | Mike Valentine (mvalentine) | Labels: | |||
| Date Opened: | 2013-06-10 14:01:12 | Date Closed: | 2013-07-16 14:50:41 | ||
| Priority: | Major | Regression? | |||
| Status: | Closed/Complete | Components: | |||
| Versions: | 1.8.20.0 | Frequency of Occurrence | Occasional | ||
| Related Issues: |
| ||||
| Environment: | CentOS 6 | Attachments: | ( 0) gdb.txt | ||
| Description: | See attached backtrace. | ||||
| Comments: | By: Richard Mudgett (rmudgett) 2013-06-10 15:25:09.162-0500 Your backtrace appears to contain memory corruption and we require valgrind output in order to move this issue forward. Please see https://wiki.asterisk.org/wiki/display/AST/Valgrind for more information about how to produce debugging information. Thanks! Since you are using at least v1.8.20, you can also use MALLOC_DEBUG as a poor man's substitute with less performance loss. Also you almost always need to compile with DONT_OPTIMIZE for any backtrace to be useful. Do you know how to reproduce this problem? By: Mike Valentine (mvalentine) 2013-06-10 15:41:44.493-0500 Unfortunately I don't yet know how to trigger this problem. It has happened a couple of times in our production environment. The backtrace I attached should have been running with DONT_OPTIMIZE, is there something about it that makes it appear that it wasn't? I will try running with valgrind in a test environment, but I don't know if I will be able to reproduce. By: Richard Mudgett (rmudgett) 2013-06-10 18:05:42.795-0500 The <value optimized out> in asterisk functions is a giveaway. You can also try MALLOC_DEBUG instead of valgrind with less performance loss. By: Rusty Newton (rnewton) 2013-06-25 16:55:35.279-0500 We'll need Valgrind output or alternatively the output of MALLOC_DEBUG to move forward with this. https://wiki.asterisk.org/wiki/display/AST/Valgrind Thanks! By: Rusty Newton (rnewton) 2013-07-16 14:50:33.714-0500 Suspended due to lack of activity. Please request a bug marshal in #asterisk-bugs on the IRC network irc.freenode.net to reopen the issue should you have the additional information requested. Further information can be found at http://www.asterisk.org/developers/bug-guidelines | ||||