[mythtv-users] mythbackend still eats memory: the current status

Udo van den Heuvel udovdh at xs4all.nl
Fri Jan 9 14:24:57 UTC 2009


Robert McNamara wrote:
> are coming across as very intractable and not at all willing to do any
> work to help.

Why misread the constructive remarks in my initial posting?

 > You may not know who has been responding to you, but
> several of them have been myth devs.  

Who have ignored the bug reports. ( no valgrind)
Who didn't do much when I ran valgrind but when it didn't work.
Who don't acknowledge the issue at all.
Who just throw it back to the one bringing it to the attention.
[ Sure, they're right to do so. I'm just another noob doing no good.
But the issue remains. ]

*** This is of course not the general behaviour of everyone but the 
overall response looks like this. ***

 > You have burned those bridges
> and I know they are no longer interested in spending an ounce of
> energy helping you with this.

How come this is the first project where this happens?
Does it say more about me or them?
Or maybe the amount of work needed?

No, I *REALLY* don't need answers, but just _think_ about that.


My setup is far from complex. It's fairly well documented.
The issues are easy to reproduce.
The issues are basic enough.
If nobody cares then it will be so until somebody does.

And we have to, very un-UNIX-y, restart our backends to free up some RAM 
every now and then.
Did you observe that also the CPU load goes up slightly?

Udo


More information about the mythtv-users mailing list