You are not logged in.
Pages: 1
The last couple of weeks I've been experiencing a problem in firefox where it suddenly starts extremely heavy disk thrashing, slowing the computer to being useless (X framerate seems to drop to 3 or 4, keyboard input heavily delayed in processing, etc etc - so much so that it normally takes several minutes to switch focus to a terminal and pkill firefox). It has "finished" - I've only stopped it by killing Firefox, but I haven't tried leaving for more than about 7 minutes.
By noting when it happened I originally assumed this was just another stupid flash bug - but I've now experienced it shortly after clicking links to hi-res images. This makes me think that the issue is actually triggered by memory allocation.
The first time it happened I took the time to look at top and it didn't appear that memory was full (so I'm thinking it probably isn't just what happens whenever my system starts swapping - and anyway there's always some stuff in swap space as I understand it). As I've been lazy and impatient I haven't done any more examination since (it really does take a long time), so I'm just posting here for now in case this is a known problem and for some advice on how to examine the problem. I'll bump with some more info when I can.
Thanks
ps: this system was hibernating while I was away for a few months so everything was updated at once a couple of weeks ago (so it's hard to tell what was the most recent change before the problem appeared).
Offline
debug output?
Offline
Pages: 1