[asterisk-bugs] [Asterisk 0012898]: Asterisk crashes sometimes, when using Mixmonitor

[noreply at bugs.digium.com]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=12898 
====================================================================== 
Reported By:                edugs15
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   12898
Category:                   Applications/app_mixmonitor
Reproducibility:            random
Severity:                   crash
Priority:                   normal
Status:                     new
Asterisk Version:           1.4.18 
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Disclaimer on File?:        N/A 
Request Review:              
====================================================================== 
Date Submitted:             06-19-2008 10:17 CDT
Last Modified:              06-19-2008 16:34 CDT
====================================================================== 
Summary:                    Asterisk crashes sometimes, when using Mixmonitor
Description: 
Hello,

I am using Asterisk 1.4.18.1, Zaptel 1.4.8, Libpri 1.4.3, Addons 1.4.5.
It's a Call Center with 30 agents running X-lite.

I am recording all calls by using Mixmonitor.

Since I've started using Mixmonitor, Asterisk crashes and restarts itself,
at least twice a day.

Is there a patch to fix this, for Asterisk 1.4.18.1 ?

I don't want to upgrade to 1.4.19 or 1.4.20, at least in this moment,
because I am using AgentCallbacklogin.

Could please help me with this issue ?

Thanks. 

====================================================================== 

---------------------------------------------------------------------- 
 putnopvut - 06-19-08 16:34  
---------------------------------------------------------------------- 
I can't be certain of this, but the problem could be the same as what ended
up being fixed in issue http://bugs.digium.com/view.php?id=11999. What I'm
seeing from your backtrace is most
likely a corruption of a frame list. In 11999, the problem that eventually
was fixed was memory corruption of a frame list. If you can, use the
11999.patch file attached to that issue and see if you still experience the
crash.

If the crash still occurs after applying that patch, then what we will
need is output from running Asterisk under valgrind. Instructions for how
to do this are in doc/valgrind.txt. Thanks! 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
06-19-08 16:34  putnopvut      Note Added: 0088971                          
======================================================================