Comment 15 for bug 343528

Upstream says they can't reproduce the bug and so need to have a reproducible test case before they'll investigate. But it sounds also like fedora runs into the same problem, so I'm guessing it's an upstream bug they just haven't dug into far enough yet.

Anyway, hopefully the patch I posted solves the issue for folks in Ubuntu at least; if not and if you'd be willing to work with upstream, please see if you can boil it down to a reproducible test case (e.g. try doing some action you think may trigger it really heavily, perhaps looped in a script).