[mythtv-users] mythbackend still eats memory: the current status
Allan Stirling
dibblah.allan.stirling at googlemail.com
Sat Jan 24 13:17:05 UTC 2009
Allan Stirling wrote:
> Udo van den Heuvel wrote:
>> AntiCat wrote:
>>> Udo van den Heuvel schrieb:
>>>> AntiCat wrote:
>>>>
>>>>> Jan Ceuleers schrieb:
>>>>> I did a 1hour recording and a 5minute recording, both with valgrind
>>>>> running.
>>>>> (The Reports are attatched to the Ticket #5545)
>>>
>>> It should be fixed with commit 19705 (trunk) or
>>> 19706 (release-0-21-fixes).
>>
>> After running a few days with svn 19714 from fixes I have these figures:
>>
>> %CPU %MEM VSZ RSS TTY STAT START TIME
>> 8.5 9.1 396948 88952 ? Ssl Jan18 97:53
>> 9.7 13.2 461016 128748 ? Ssl Jan18 252:16
>> 10.2 14.9 478488 145068 ? Ssl Jan18 411:36
>> 10.4 16.2 491164 157904 ? Ssl Jan18 572:08
>> 10.7 17.9 507172 174568 ? Ssl Jan18 739:58
>> 10.8 19.3 521604 188232 ? Ssl Jan18 902:52
>>
>> Older numbers at the bottom.
>> These figures tell me that indeed EIT was not the main source of
>> memory leaks on my system.
>> BTW: Do the numbers grow quicker than before?
>> What do you think?
>>
>> In other news: I have the AMD Thunderbird system ready and waiting,
>> with disks etc to run a test system on.
>> Only issue is a (faked?) video stream to simulate the multirec
>> situation. How could I accomplish this?
>
And in incredibly bad mailing list form, I'm following up to
my own email to add the valgrind command that gives the most
information:
valgrind --leak-check=full --show-reachable=yes mythbackend
(You will have to terminate this manually at the end of the
4 hours with CTRL-C)
Cheers,
Allan.
More information about the mythtv-users
mailing list