[mythtv-users] Is this a bug in Mythbackend? Was: Backend crash with malloc(): memory corruption (fast)

[tim dennis]

This bug occurs sooner when the backend is hard at work, either commercial
flagging, serving media to a frontend, recording multiple tuner The more the
backend is doing the sooner the Malloc Bug will occur. However, even if the
backend is at rest it will eventually trip up on the memory allocation and
die.

Disabling the commercial flagging is like you say only delaying the
inevitable.

As suggested in a different post I am now running the backend in a terminal
window with the following command:

MALLOC_CHECK_=3 mythbackend

Suggest you do the same and report back error messages when mythbackend bugs
out.

t.dennis
(mythbackend version: 0.21.20080304-1)


On Sun, Feb 1, 2009 at 2:50 PM, Taco Mel <taco_mel at yahoo.com> wrote:

> >>> Yes, I ran memtest and besides, all the research I did says this is a
> >>> programming error message, not bad memory.  It is generated by C upon
> >>> its detecting some memory allocation error, like trying to access
> >>> memory that has been released.  It does sound like a message for bad
> >>> memory but it apparently has nothing to do with that.  The program
> >>> shut down, the system didn't crash.  All signs point to it being a bug
> >>> as far as I can tell.
> >>>
> >>> Allen
> >
> > Wow, that is much worse than what I am seeing.  I have only had two of
> > these in 5 months.  Please let me know if you
> > make any progress on this.  It isn't high priority with me right now
> > but sounds like you will be solving it soon.
>
> I was seeing this error message (and noticing corresponding mythbackend
> crashes) around 5-10 times a day.  I have reduced this to about 1 crash
> every 2 days by disabling commercial flagging on the backend (and enabling
> it on a slave backend).  This certainly reduced the amount of output in the
> log (damaged over-the-air MPEG streams and various decoding errors related
> to h.264).  I don't know for sure if this is what actually "improved" the
> backend crashing situation, but it did substantially reduce the amount of
> stuff being logged by the master backend.
>
>
>
>
> _______________________________________________
> mythtv-users mailing list
> mythtv-users at mythtv.org
> http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mythtv.org/pipermail/mythtv-users/attachments/20090203/7e054a2f/attachment.htm>