[asterisk-bugs] [Asterisk 0015109]: Abort by memory allocator, possibly in moh_files_generator
Asterisk Bug Tracker
noreply at bugs.digium.com
Thu Jul 2 23:31: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-02 23:31 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...
======================================================================
----------------------------------------------------------------------
(0107380) russell (administrator) - 2009-07-02 23:31
https://issues.asterisk.org/view.php?id=15109#c107380
----------------------------------------------------------------------
Thanks for the updated backtrace and valgrind output. Unfortunately, there
isn't actually much in the valgrind output that we can do anything with.
The errors at the beginning happen at startup and are expected. Then, the
end is a memory allocation summary after Asterisk was stopped.
Mark and I have both put a lot of time into looking at the related code
and trying to come up with what might be going wrong. We haven't come up
with anything more yet. If we do, we will certainly post an update here.
Issue History
Date Modified Username Field Change
======================================================================
2009-07-02 23:31 russell Note Added: 0107380
======================================================================
More information about the asterisk-bugs
mailing list