Rich Braun wrote: > I can make it go away for that short amount of time by killing > and restarting the browser, but a day later Firefox is /always/ painfully slow > -- thrashing through memory (not disk) in some inefficient piece of core code.
This doesn't fit your description, but one of the inefficiencies in FF is that it writes out the sessionstore.js file (session data for crash recovery) in its entirety every 10 seconds, which can cause a very noticeable hang once your session has grown. This happens after any action that alters the session, and that can include an action as innocuous as scrolling in a page. I often have 50 to 60 tabs open and after a day or so, FF does get annoyingly slow. One thing I really don't like in Chrome is the bookmark manager. The FF manager was bad enough at being feature sparse, and the Chrome one is even more so. It doesn't even support saving notes with a bookmark, which I often use. What's worse is that Chrome doesn't interoperate with FF's bookmark manager - you can't drag a link from Chrome to the FF bookmark manager. So you can't relegate FF to being just a bookmark manager, while using Chrome for browsing. -Tom -- Tom Metro Venture Logic, Newton, MA, USA "Enterprise solutions through open source." Professional Profile: http://tmetro.venturelogic.com/ _______________________________________________ Discuss mailing list [email protected] http://blu.org/mailman/listinfo/discuss
