Test: Firefox’s new Plugin Container Process

With the latest / since Firefox 3.6.4 plugins are run in their own process. That’s great news because it will help to gain more stability. And it opens a lot of new possibilities. For example you can create your own plugin process loader *gg*.

I wanted to remove the plugin loader binary (plugin-container.exe on windows in the Firefox program directory) but only removing it (or replacing it with a same-named directory) did not work. Then I replaced it with a exe file which just does nothing. But this does not work at all, Firefox freezes in all these three scenarios.

Looks to me that this Gecko OOPP feature isn’t properly implemented in Firefox. It only handles the case that this process crashes but it can not deal with the case there is nothing to start?

Update: Filled a Bugreport on Mozilla: Bug 574316<

Update 2: My Bugreport is a duplicate of Bug 535077 (Failing to exec() mozilla-runtime (plugin-runtime) for a sync launch causes Gecko to hang) which contains more information on the topic.

Read On: HTML Entity Boundaries – Zero Padding

This entry was posted in Pressed, Surviving the Internet and tagged , , , , , , , , , , . Bookmark the permalink.

3 Responses to Test: Firefox’s new Plugin Container Process

  1. Steve Toffen says:

    I recently upgraded to the version of Firefox that has the plugin-container.exe file included. It appears to take tons of my PC’s memory and thus slowdown my browsing. I am either going to an older version or finding a new browser vendor. The plugin-container.exe combined with the amount of ram that Firefox is hogging makes the system unbearable now.

    • hakre says:

      Well that might not be related to the container.exe but to the plugin that exe is loading. Basically it is there to only load the plugins. So before that release, firefox did load the plugins directly (and would therefore consume the memory). Now all plugins are loaded by this plugin-container.exe and this process consumes the plugins memory now.

      So downgrading might not have the effect you wish to achieve. Instead I suggest you start to block plugins with an Add-On like noscript.

  2. xeromem says:

    open about:config search for and toggle to disable:
    dom.ipc.plugins.enabled.npswf32.dll <—-set to false to disable plugin-container.exe

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s