Comment 39 for bug 20765
Revision history for this message
|
|
#39 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
f33e652
(Get the code!)
(In reply to comment #25)
> Except sometimes, I start getting [delays] on _all_ URLs in all
> window and have to restart Firefox to get rid of it...
This sounds a lot like symptoms I reported in Bug 233872:
https:/
My guess is that the underlying problem is in memory allocation code that wraps the OS memory allocation system calls (assuming Mozilla has its own malloc wrappers) or some higher layer abstraction, like an in-memory database (doesn't Mozilla use RDF structures for a bunch of things?). The "threshold" I referred to seemed to vary depending on the platform, and what extensions are loaded, but usually using the browser for an extended period or stressing it by loading complex pages will cross the threshold, after which performance tanks. The problematic code may be part of the JS engine, as sites that have JS complexity are more likely to trip the threshold, and once past the threshold, UI interaction that is implemented in JS (like switching tabs) crawls. It could be due to some inefficient code similar to Bug 40988, except instead of speed decreasing exponentially as number of DOM nodes increases, it may be relative to some other internal memory structure.
The situation has gotten so bad with my current FF installation (I haven't determined whether it is FF 2.0 itself, or the increased quantity of extension) that I've had to reserve using FF for development, and have switched to using a (ironically) light-weight Seamonkey installation for day-to-day browsing.
-Tom