[mythtv-users] `Mythbackend leaks memory` continued

[Udo van den Heuvel]

Nick Rout wrote:
> IIRC Udo was using his backend to record a number of channels
> continuously, like every programme! That seems to be the only
> difference in his system identified to date.

I just use mythtv to record.

> So its an "edge" case,

Indeed, a very extreme difference.

> that "normal" use may not throw up. Errors that ideally should still
> be fixed, but that may have a lower priority to errors that affect
> many more users (resources being finite and all that).

Why speculate on that when we even don't know WHERE the error is or WHAT
is wrong. Or HOW we can find out what is wrong where when we can't run
valgrind?

If the code is valgrind-proof under 'normal' use the error must be in
the code that has to do with my peculiar use of MythTV.
I limit the scheduler to 8 hours ahead with some SQL.
I use multirec.
Also I use three searches, one for each channel. Maybe I could combine
these and see a different memory growth rate?
What ideas do you have?

> But steady growth in memory use doesn't necessarily imply a leak,
> mightn't it be that there is simply a lot of buffers used, which will
> get thrown away eventually. The process still only seems to have a
> %MEM of 19.9 on the last reading.

Just hope it doesn't crash.
It may reach the 40% I mentioned earlier.
It just continues to grow. It doesn't get smaller.
Please believe me.

Kind regards,
Udo