Q&A with Firefox's Blake Ross
dotlin writes to tell us the Seattle PI is running a lengthy and interesting interview with Firefox's Blake Ross. In the interview Ross addresses many of the issues surrounding the future of Firefox including their attempt to streamline Firefox in 2.0, the feature comparison between Firefox and IE, different ways of measuring browser market share, and many more.
There are lots of extensions with memory leaks and other serious problems. Be sure you're not using an extension on that list if you're having problems.
Plugins, especially Flash, have also been known to cause problems such as high memory use and 100% CPU use after waking up from hiberation. Be sure to get the latest Macromedia, Java, and Acrobat plugins.
What a fool believes, he sees, no wise man has the power to reason away.
Of course! They've written the Leak Monitor extension to help extension authors to find leaks in their extensions. As far as I know, there's no way to limit the memory an extension uses without causing additional problems, or to kill an extension that's using too much memory. If you have a detailed suggestion for how extensions or plugins could run in their own processes, perhaps you should explain it.
What a fool believes, he sees, no wise man has the power to reason away.