[asterisk-bugs] [Asterisk 0015109]: Abort by memory allocator, possibly in moh_files_generator
Asterisk Bug Tracker
noreply at bugs.digium.com
Wed Jul 22 08:05:13 CDT 2009
A NOTE has been added to this issue.
======================================================================
https://issues.asterisk.org/view.php?id=15109
======================================================================
Reported By: jvandal
Assigned To:
======================================================================
Project: Asterisk
Issue ID: 15109
Category: Resources/res_musiconhold
Reproducibility: random
Severity: block
Priority: normal
Status: acknowledged
Target Version: 1.4.27
Asterisk Version: 1.4.24
Regression: No
SVN Branch (only for SVN checkouts, not tarball releases): N/A
SVN Revision (number only!):
Request Review:
======================================================================
Date Submitted: 2009-05-14 10:49 CDT
Last Modified: 2009-07-22 08:05 CDT
======================================================================
Summary: Abort by memory allocator, possibly in
moh_files_generator
Description:
I have a server running with Asterisk 1.4.24.1 where it randomly segfault
for "unknown" reason.
I'm not sure if this is related to moh_files_generator function or with
filestream_descructor.
Let me know what needed in order to fix this crash, if GDB traces aren't
enough.
Asterisk is compiled with DONT_OPTIMIZE and others flag needed for "gdb".
======================================================================
Relationships ID Summary
----------------------------------------------------------------------
related to 0014958 Segfault Asterisk 1.4.24.1
related to 0015123 out of bounds crash and core dump
has duplicate 0015195 double free or corruption (!prev) in mo...
======================================================================
----------------------------------------------------------------------
(0108071) aragon (reporter) - 2009-07-22 08:05
https://issues.asterisk.org/view.php?id=15109#c108071
----------------------------------------------------------------------
I'm still gettings logs like this in valgrind.txt while trying to debug
another 1.4.26 crash https://issues.asterisk.org/view.php?id=15544
Using r206273
This info looks different than previous valgrind output and I am not
experiencing any crashes without valgrind...
==12561== Thread 53:
==12561== Invalid read of size 4
==12561== at 0x80B4B62: __frame_free (in /usr/sbin/asterisk)
==12561== by 0x80B4CBA: ast_frame_free (in /usr/sbin/asterisk)
==12561== by 0x46D4396: moh_files_generator (res_musiconhold.c:295)
==12561== by 0x808B79B: ast_read_generator_actions (in
/usr/sbin/asterisk)
==12561== by 0x808D179: __ast_read (in /usr/sbin/asterisk)
==12561== by 0x808D421: ast_read (in /usr/sbin/asterisk)
==12561== by 0x8079BD0: autoservice_run (in /usr/sbin/asterisk)
==12561== by 0x8121A6D: dummy_start (in /usr/sbin/asterisk)
==12561== by 0x8B249A: start_thread (in /lib/libpthread-2.5.so)
==12561== by 0x80942D: clone (in /lib/libc-2.5.so)
==12561== Address 0x42386b8 is 400 bytes inside a block of size 872
free'd
==12561== at 0x400562C: free (vg_replace_malloc.c:323)
==12561== by 0x80728BA: __ast_free_region (in /usr/sbin/asterisk)
==12561== by 0x80732AC: __ast_free (in /usr/sbin/asterisk)
==12561== by 0x8074B19: ao2_ref (in /usr/sbin/asterisk)
==12561== by 0x80B35CB: ast_filestream_frame_freed (in
/usr/sbin/asterisk)
==12561== by 0x80B4B5E: __frame_free (in /usr/sbin/asterisk)
==12561== by 0x80B4CBA: ast_frame_free (in /usr/sbin/asterisk)
==12561== by 0x46D4396: moh_files_generator (res_musiconhold.c:295)
==12561== by 0x808B79B: ast_read_generator_actions (in
/usr/sbin/asterisk)
==12561== by 0x808D179: __ast_read (in /usr/sbin/asterisk)
==12561== by 0x808D421: ast_read (in /usr/sbin/asterisk)
==12561== by 0x8079BD0: autoservice_run (in /usr/sbin/asterisk)
Issue History
Date Modified Username Field Change
======================================================================
2009-07-22 08:05 aragon Note Added: 0108071
======================================================================
More information about the asterisk-bugs
mailing list