[mythtv-users] Is this a bug in Mythbackend? Was: Backend crash with malloc(): memory corruption (fast)
allen.p.edwards at gmail.com
Mon Jan 26 21:36:10 UTC 2009
On Mon, Jan 26, 2009 at 12:54 PM, Francis Hartojo <fhartojo at gmail.com> wrote:
> On Fri, Jan 23, 2009 at 8:50 AM, Allen Edwards
> <allen.p.edwards at gmail.com> wrote:
>> Is this a bug in Mythbackend? Details from old post are below. From
>> the error log and some web searches, it seems to be a programming
>> error. According to my web searches, many others have seen this and
>> nobody has any good suggestions. I am thinking I should report this
>> but wanted to pass it by the group first.
> I take it you've run memtest to make sure it's not a bad RAM? The
> last time mythbackend crashed left and right for me it was because of
> a bad RAM pair.
> FWIW. HTH.
> echo "sunegbwb at tznvy.pbz" | tr '[a-z]' '[n-za-m]'
> mythtv-users mailing list
> mythtv-users at mythtv.org
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.
More information about the mythtv-users