Slashdot Mirror
Firefox 3.6.4 Released With Out-of-Process Plugins
DragonHawk writes "Mozilla Firefox 3.6.4 went to general release today. The big new feature in this release is out-of-process plugins (OOPP). This means things like Flash, Java, QuickTime, etc., all run in separate processes, so when Flash decides to crash, it won't take your browser out with it. If Flash starts consuming all the CPU it can find, you can kill it without nuking your browser session. I've been using this feature since it was in the 'nightly build' stage, and it was still more stable than 3.6.3, just because Flash was isolated." And reader Trailrunner7 supplies another compelling reason to download 3.6.4: "Security researcher Michal Zalewski has identified a problem with the way Firefox handles links that are opened in a new browser window or tab, enabling attackers to inject arbitrary code into the new window or tab while still keeping a deceptive URL in the browser's address bar. The vulnerability, which Mozilla has fixed in version 3.6.4, has the effect of tricking users into thinking that they're visiting a legitimate site while instead sending arbitrary attacker-controlled code to their browsers."
I have never had problems with firefox having a ton of tabs open.
I regularly have 15+ tabs, sometimes 50 or 60. The only time I have any issues is if I turn off no script and get some flash or javascript running to slow things down.
I confused, since I am on Kubuntu 10.04 64-bit version, and use the Firefox version that comes with that release (3.6.3).
For the longest time, I am able to kill npviewer.bin without Firefox crashing. I just get a grey box when I do that where Flash used to be.
Flash already runs as a separate process for me.
Here are the processes:
So, what is happening here?
2bits.com, Inc: Drupal, WordPress, and LAMP performance tuning.
This, this, this, this, this. The terrible user interface responsiveness of Firefox is what kept me on IE for the longest time (and I only moved because of addons, not because Firefox itself is any better).
For a good test, open a Slashdot story with ~1000 comments and watch as the browser just stops dead in the water for 5-15 seconds while it renders the page. You can also try opening the browser when you have 10 or more tabs saved in your session. Again, the entire interface is useless while the pages are rendering. If the browser really is multithreaded in any meaningful fashion, then the rendering threads obviously have a priority higher than the UI, which seems like a bad thing.
I'd rather have this improved than move plugins into an external process. Since I started using NoScript I haven't had Firefox crash because of Flash. Ever. However, I still read Slashdot so I do deal with the lagging on a regular basis.
"What do you despise? By this are you truly known." --Princess Irulan, Manual of Muad'Dib
/)
For performance reasons, tabs don't and shouldn't run in separate processes.
I find that statement dubious. Please explain.
In my experience, the process-per-page (be they tab, window, or whatever) yields much better performance. I believe there are multiple reasons for this. For starters, the OS already has a perfectly good scheduler, and it makes sense to use that to handle multi-tasking. Indeed, OS people prolly know more about how to design a scheduler than browser people. By exposing the this to the OS, it also means the OS can do whatever tricks it has to make I/O, memory allocation, etc., more efficient on a per-page basis, rather than treating the whole browser as an opaque object.
Finally, lot of modern hardware has 2, 3, 4 or more processor cores. Firefox generally only uses one of them. A browser like Chrome can have each page render on its own processor core, which is a *huge* performance gain. Without that, any multitasking is going to be limited to slicing up a single core between multiple tasks. The system can still only do one thing at a time. By using multiple cores, the system actually gets multiple things done literally simultaneously. On good hardware, the performance difference is astounding.
"You know, the original motivation for the tabs feature was that each tab could be run in a separate thread whereas each window needs a separate process."
That's just plain wrong. Each window does not need a separate process. Each tab does not get a separate thread. In Firefox 3.6, multiple threads are used, but it's not a one-thread-per-tab thing. Most of the work is still done in a single monolithic thread.
The motivation for tabs in Firefox was to copy Opera. The motivation for tabs in Opera was as an alternative to one-page-per-window or MDI.
dragonhawk@iname.microsoft.com
I do not like Microsoft. Remove them from my email address.
I've been using Opera, Google's Chrome, and IE alongside Firefox on W7 for about four months now on three computers, on a consistent basis, meaning every day.
Opera is a bit faster, Chrome is a lot faster, but we are talking about tenths of a second here when rendering anything other than extremely complicated web pages which to be honest would render a lot faster in any browser if the designers wouldn't include so much crap in them that demands connections to multiple websites for stupid things like a small advertising gif image from a server that is already overloaded.
Over that time, Firefox has been easily the most stable browser I've ever used - that might have something to do with me running addons such as adblock, flashblock, and NoScript - denying access to a lot of the poorly written or implemented crap websites that can crash any browser. I can count the number of times that Firefox has crashed on all three of my computers on one hand since the beginning of the year - that's two laptops and one desktop, running combinations of Windows XP, Windows 7, Ubuntu and Fedora.
It didn't used to be that way, no. But it is now. Firefox also consistently recalls my previous browsing sessions - even after the multiple downtimes I had tonight during numerous power outages due to bad storms (the new battery for the UPS is in transit and should arrive tomorrow, and I ordered it from a website that does not list Firefox in their supported browsers list) neither Opera nor Chrome did so.
The addon Xmarks has proven to be both useful and consistently stable, I'd highly recommend it.
YMMV, YEMV, etc. This is just mine. I don't know about the rest of you, but I'll take stable over fast any day. I regularly have from a dozen to several dozen tabs open at any one time, and being able to recover my work after any crash, no matter the cause, means a lot to me. These features should have been written into browsers as DEFAULT features from the beginning. Somewhat around ten years ago I remember wishing that someone would just code a browser that could remember what I was doing before a crash, and do so consistently. Now, finally, I have one. Thank you, Mozilla.
What I find ironic about the whole browser war is that the "feature leader" over the last decade has been the open source solutions - specifically firefox, and the rest of the field is playing catchup - especially Microsoft.
SB
It's old. The more humans I meet, the more I like my cats. At least they are honest.