There are a couple of threads in the forums about the bug(s?). One such thread 
is at http://www.ubuntuforums.org/showthread.php?t=193283 .
Here's the summary:

Problem occurs with the nv driver and the official nvidia drivers. There
is also an ATI user having the same issues, so it doesn't look like a
driver issue. It's not a Firefox issue as the exact same binaries on a
Mandriva system (and same hardware) do not produce the problem. Someone
else reported the same thing running both Dapper and FC5. FC5 doesn't
have the problem, Dapper does. The problem is also reported with
Thunderbird, VMware, and even Opera. A few other programs were mentioned
too.

I have swap working, so it's not a swap problem (although not having
swap working can be a problem!). On thing I have done and I've not seen
reported is I've kept top running in a terminal. I notice that the
amount of memory xorg uses slowly climbs and never comes back down, even
if I close Firefox. It climbs every time Firefox does a "page refresh"
(on it's own, BTW).

I left Firefox open all night with only a simple static page. At the
start, xorg was using a little less than 2% of my memory. By morning, it
was up to 39% (as reported by top)! No flash or Java on the page either
and only a few terminals running in the background (one with top).

I'm thinking it is a bug in xorg, maybe a memory leak. I had this
problem in Breezy as well as Dapper (what I'm running now).

-- 
[Dapper] Firefox hard locks when RenderAccel is enabled
https://launchpad.net/bugs/6279

--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to