Comment 16 for bug 6279
Revision history for this message
| berzerke (robert-spotswood-computer) wrote | #16 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
There are a couple of threads in the forums about the bug(s?). One such thread is at http://
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).