[mythtv-users] Gradual frontend slowdowns, Was: Is it worth while to stop/start mythtv nightly?)

[James Thorpe]

On 08/11/2010 08:46, James Thorpe wrote:
> On a similar note, and one I keep meaning to bring up on here but 
> never seem to get round to it...
>
> I find that after a few days use, I HAVE to restart my frontend - it 
> just gets too slow to use - menu navigations (even just going up and 
> down on a single menu) take some time, and waiting for live tv / a 
> recording to start even longer.  I've seen the same behaviour from 
> 0.22 through to 0.23-fixes - whenever I think about mentioning it, 
> there's always a new release around the corner that I hope might fix 
> whatever it is - in this case 0.24!
>
> Has anyone else seen this behaviour at all?  It's running Mythbuntu 
> (currently 10.04) on an Acer Revo.
>

On 08/11/2010 20:08, Robert Longbottom wrote:
> On 08/11/2010 13:06, David Asher wrote:
>> I have a nearly identical setup hardware-wise, but I'm running 
>> Mythbuntu 9.04 using PXE boot and no swap.  I've had to have a 
>> cron.daily job kill my frontend every day @ 4am (it auto restarts via 
>> a script upon exiting).  If I don't do this mythfrontend's virtual 
>> size grows too large to spawn the gnome-screensaver --poke command 
>> and eventually the screen goes blank and stays blank.  I'm running 
>> mostly up-to-date 23-fixes with the Mythbuntu theme.
>>
> I see this too with Mythtv-0.23-fixes on Gentoo.  Over time 
> mythfrontend memory usage grows, making the frontend slower and 
> slower.  Eventually it usually crashes if I'm patient and leave it, or 
> I restart it.  Seems to vary how long it takes to get to an unusable 
> state.  I've never put any effort into trying to find out why though.
>

Ok, so it seems it's not just me then, and looks like it'll be 
worthwhile trying to find out what's going on for the benefit of 
others.  I'm not really an expert in these manners, but am quite happy 
to try to debug where I can.  Bearing in mind that when this happens, 
its generally because other people in the house are trying to watch 
stuff so ideally I need to gather information quickly before restarting 
again.  What would be the most beneficial steps to take in this 
situation?  Should I run the frontend with a different set of logs 
enabled to the default etc?  Or should I do what I keep doing and wait 
until I upgrade to 0.24 to see if it even still happens?

Thanks,
James.