Facebook Plunges Again
Tumblr 101: Tips And Tricks To Get Started
Mozilla taps Google Chrome source code to bring multi-process plugins to Firefox
Yes, the same superpower which prevents Google Chrome from tanking entirely when a single plugin bites the dust are now built in to Firefox's core as well. In fact, it's built in using some of the open source Chromium code.
The feature is disabled by default for now, so to switch it on you'll have to head to your about:config and change the dom.ipc.plugins.enabled value to true. After you restart Minefield, pulling up task manager should show you that your plugins are now running in their own process.
It's not one-tab-per-process yet, but it's a start - and a sign that Mozilla fully intends to keep pace with Google Chrome.
Comments
13
Subscribe to commentsNickDec 16th 2009 4:58PM
This is exactly what Google wants.
They leave specific technologies through FOSS.
Because of that, (third party) software develops along the paths Google desires.
Lee MathewsDec 16th 2009 5:00PM
True, Nick.
Google always says they want "a better web" so that services can really shine. If they leave code which allows their services to perform better open and other browsers integrate it, so much the better.
In the end, it makes things like GMail and YouTube more stable, faster, etc. etc.
Rune StarDec 16th 2009 5:04PM
What is that '' arrow thing on the Task Manager's Title Bar in the screenshot?
btw, glad to see Firefox is doing this... Lately my firefox is crashing multiple times a day.
Lee MathewsDec 16th 2009 5:04PM
That's TeamViewer's single-window sharing icon ;)
Rune StarDec 16th 2009 5:44PM
Oh, a remote access app, cool thanks. :)
SilverWaveDec 16th 2009 7:25PM
You are doing something wrong.
firefox -p will let you create a new profile - then add your addon back in one at a time.
I _never_ get a crash with ff.
SilverWaveDec 16th 2009 7:28PM
try a ready built profile from here:
http://www.instantfox.com/
JoshDec 16th 2009 5:04PM
Doesn't seem to work in the Mac version.
Kris120890Dec 16th 2009 5:46PM
What build are you using it doesn't work for me.
PhylopDec 16th 2009 8:22PM
For some reason in Firefox 3.6 Beta 4 I can't find dom.ipc.plugins.enabled. Anyone else have that trouble?
danielkzaDec 16th 2009 8:38PM
It's not on 3.6, only in the source control trunk: you'll need one of the recent nightly builds based on it. (a.k.a. 3.7).
pujaDec 17th 2009 12:49AM
for tabs there's already the dom.ipc.tabs.enabled value, but changing it to true doesn't trigger anything (for me at least) - maybe a hint to some very soon to come one-tab-per-process
pujaDec 17th 2009 2:03AM
btw, enabling the separate process for plugins breaks fullscreen functions of flashplayers (like on youtube) - the video gets fullscreened in the background, while firefox stays in the foreground