[mythtv] [mythtv-commits] Ticket #3317: mythbackend memory leak
Stuart Auchterlonie
stuarta at squashedfrog.net
Mon May 7 19:17:03 UTC 2007
Kevin Kuphal wrote:
> MythTV wrote:
>> #3317: mythbackend memory leak
>> -----------------------+----------------------------------------------------
>> Reporter: anonymous | Owner: stuarta
>> Type: defect | Status: new
>> Priority: minor | Milestone: 0.21
>> Component: mythtv | Version: head
>> Severity: medium | Resolution:
>> -----------------------+----------------------------------------------------
>>
>> Comment(by Jeremy Green <jaggroups at brownout.com>):
>>
>> Well, the backend seems to still be using an ungodly amount of memory:
>>
>> 10970 mythtv 15 0 1577m 1.3g 14m S 0 64.0 4:44.61 289m
>> mythbackend
>>
>> This less than a day after I started it with --noupnp
>> So, I don't know how much of the upnp code this disables but it disables
>> it all then that seems to imply that the problem is elsewhere. Right?
>>
>>
> I'd just like to comment that I too am seeing this behavior on R13352.
> mythbackend was showing about 1g of RAM after maybe 2 or 3 days of
> operation. At this point I started getting problems forking
> mythcommflag processes so none of my commercial flagging was working.
> Restarting the backend immediately dropped it down to 262m of virtual
> RAM. If there is anything I can do to provide additional data or
> debugging, please advise.
>
Can you run a debug build under valgrind for a while and try to provoke
it with whatever devices you have on your network.
You'll need the following magic incantation
valgrind --tool=memcheck --error-limit=no --show-reachable=yes
--log-file=valgrind-mythbackend.log --leak-check=full -v -- mythbackend
<any usual backend options> | tee backend.log
Probably need to run it for a few hours if possible
Thanks
Stuart
More information about the mythtv-dev
mailing list