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

[Gavin Hurlbut]

On Mon, Nov 29, 2010 at 9:13 AM, Udo van den Heuvel <udovdh at xs4all.nl> wrote:
> That might be the case but that number grew since that period.
> Why?
> The app has been recording for a while before then and since then so why
> would it allocate more memory?

Because other things may have changed...  Like scheduling
information..  Who knows.  That in and of itself is not indicative of
a memory leak.

> Same feed as ever, same updating schedule, same source, same multiplex,
> same stations, etc, etc. Same.

Really?  So your stations air the identical show lineup every day?  I
didn't think so.

>> If you are going to claim that we are leaking memory, you need to
>> prove it.
>
> You might as well explain why it isn't leaking, that would be easier.
> I just see numbers increasing when I do not expect them to be increasing
> (after a `short` while of running...).

If you can't show (with the proper tools) that it is leaking and
where, you might as well just give up.  I can't use a crystal ball and
tell you where in the hundreds of thousands, if not millions, of lines
of code there is a leak.  That's why we have tools to tell us.  And I
can not reproduce your exact setup.  It could be there is a leak
specific to how you use the system.  The only one who can properly
instrument it is you.

Asking me to explain why your accusation is false is bogus.  You make
the accusation, you prove it.  And proof means valgrind output, not ps
snapshots.

>> kilobytes, which really isn't terribly significant.
>
> A leak is a leak.

Whatever.  If you are worried about the equivalent of a liter of water
leaking from a very large lake, you are wasting your time.  A few
kilobytes out of a memory footprint of 1+GB is miniscule, and the
amount of time spent trying to fix it is not worth the trouble.  We
have better things to spend our time on.