[asterisk-bugs] [Asterisk 0015109]: Abort by memory allocator, possibly in moh_files_generator
Asterisk Bug Tracker
noreply at bugs.digium.com
Wed Jul 8 08:32:34 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-08 08:32 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...
======================================================================
----------------------------------------------------------------------
(0107480) aragon (reporter) - 2009-07-08 08:32
https://issues.asterisk.org/view.php?id=15109#c107480
----------------------------------------------------------------------
I cant keep valgrind running long enough without a crash to continue
debugging bug 15109. I keep getting crashes caused by
https://issues.asterisk.org/view.php?id=15396 Asterisk crashed under
Valgrind on that bug report so I uploaded valgrind trace. Then I started
Valgrind/Asterisk again to hope for 15109 crash under Valgrind.
I hope a developer can look at
https://issues.asterisk.org/view.php?id=15396 so I can continue to work on
15109 but to be honest 15396 is a much more serious bug.
Issue History
Date Modified Username Field Change
======================================================================
2009-07-08 08:32 aragon Note Added: 0107480
======================================================================
More information about the asterisk-bugs
mailing list