Mozilla enabled multi-process plugin support in Firefox recently which has plugins run in their own process separated from the browser
Only Microsoft's Internet Explorer and the Google Chrome web browser are full multi-process web browsers at the time of writing.
Multi-process refers to the use of multiple processes on the operating system for browser functionality. In the case of Firefox, that is one process for the browser core and another for plugins. Google Chrome uses multi-processes for individual websites and other contents as well taking it yet a step further than Firefox.
While a multi-process architecture impacts RAM use, it is beneficial for stability. If a plugin crashes, it won't take the whole browser with it for instance as only its own process is terminated eventually.
Mozilla announced last year that it made the decision to introduce multi-process support in the Firefox browser.
The first step towards the goal has now been introduced in the latest Firefox Nightly version, the cutting edge development version of Firefox.
Firefox will separate plugin content, Adobe Flash for example, from the main browser process to improve stability and security. Firefox users who check the task manager or another process manager will notice a Firefox process, and additional processes for plugins that are running.
This new feature is currently available only for Firefox for Linux or Microsoft Windows. It comes with a few issues that the developers are aware of including:
The plugin-crash UI is not finished. The current UI is just a non-localized dialog so that we can get crash reports from nightly testers. This will be changed soon!
On Windows, tearing/repainting issues when scrolling, bug 535295
On Linux, compiz effects and Flash don’t work together on some systems, bug 535612
On Windows, selecting “Print” option in Flash may lock up Firefox, bug 538918
On Windows, hulu won’t switch to full-screen mode, bug 539658
On Linux with GTK+-2.18 or later, GDK assertions and a fatal XError, bug 540197
Firefox-process crashes at NPObjWrapper_NewResolve with silverlight and sometimes Flash, bug 542263
Firefox users who want to test the new multi-process architecture are asked to submit any bugs that they find to Bugzilla so that the developers can analyze and remove them from the web browser.
The new feature can be disabled by setting the Firefox preference dom.ipc.plugins.enabled to false. (via Benjamin Smedbergs)
Update: Things have changed a bit since 2010. The mozilla runtime process that you see on the screenshot is not used anymore. You will see Flash plugins displayed directly instead.
As you can see, multiple FlashPlayerPlugin processes are launched when you run Flash content in Firefox.
Advertising revenue is falling fast across the Internet, and independently-run sites like Ghacks are hit hardest by it. The advertising model in its current form is coming to an end, and we have to find other ways to continue operating this site.
We are committed to keeping our content free and independent, which means no paywalls, no sponsored posts, no annoying ad formats or subscription fees.
If you like our content, and would like to help, please consider making a contribution:
Ghacks is a technology news blog that was founded in 2005 by Martin Brinkmann. It has since then become one of the most popular tech news sites on the Internet with five authors and regular contributions from freelance writers.