Comment 332 for bug 620074

The bug I'm seeing is extremely reproducible. (I just wait for about a day with firefox running and lots of tabs open and it will happen) As I mentioned it occurs when memory pressure starts forcing things into swap. This is not a hard lockup and the system will eventually recover. (Where "eventually" can be > 30 minutes)

updated and trackerd also cause my system to be unusable, as reported above. I have disabled them as a consequence...

Given that I can trigger it, I can run jobs in the background that could log something useful...locks? fsync? What do you suggest?

(This system has a quad core intel and raid5 root as well -- don't know if that's related)