How to register a global hotkey for your application in C#

How to register a global hotkey for your application in C#

Register a hotkey for your application that can be triggered even if your form is minimized and does not have focus. More »

Visual Studio 2013

Visual Studio 2013

Visual Studio 2013 is now available. Make sure to upgrade to the latest version of Visual Studio. More »

How to download a file in C# (progressbar and download speed)

How to download a file in C# (progressbar and download speed)

Learn how to download files in C# while displaying the percentage and the download speed. More »

UDP hole punching implementation in C#

UDP hole punching implementation in C#

Learn how to implement UDP hole punching so you can make your clients life a lot easier by not forcing them to open ports on their end. More »

 

How to disable plugin-container

Plugin-container.exe is a Firefox process that is used to load plugins separately so if a plugin crashes for whatever reason, Firefox won’t be affected by the crash and will stay responsive.

Since there are a lot of people experiencing problems with the plugin-container process I wanted to provide you with two easy methods for disabling it.

In older versions of Firefox it was possible to disable plugin-container.exe by following the steps below.

First method

  1. Enter about:config in your address bar
  2. Search for dom.ipc.plugins.enabled
  3. Set their values to false

Sadly the above method doesn’t seem to work anymore with the newer versions of Firefox. Luckily there is a different workaround which can achieve the same exact result by setting a system or a user environment variable. Follow the steps below if the first method did not work for you.

Second method

  1. Right click on your computer icon on the desktop and click properties
  2. Go to Advance system settings
  3. Click the button called "Environment Variables"
  4. Click the “New” button under User variables or System variables depending if you want the change to affect all the users on the system or just the one you are currently logged as
  5. Set the variable name to MOZ_DISABLE_OOP_PLUGINS and its value to 1

And that is all you have to do. Now simply restart Firefox and you will notice that the plugin-container.exe process will not be used any more.

    25 Responses to How to disable plugin-container

    1. xfN03gek says:

      Normally I do not read post on blogs, but I wish to say that this write-up quite forced me to try and do so! Your writing style has been surprised me. Thanks, quite good post.

    2. Skafandri says:

      Normally i dont comment/reply Blogs or Posts, but i wish to say: You saved my CPU!!

    3. Brian Daniels says:

      Thank you CooLMinE. My wife’s CPU has been liberated. Thanks for posting this.

    4. PHAM NGHIA says:

      thank you member sended post

    5. Albertarocks says:

      Thanks CooLMinE. That damned plugin container has been hounding my machine since forever… up until now. Happy New Year.

      • CooLMinE says:

        I know the feeling, first Firefox’s plugin container then flash’s FlashPlayerPlugin process! Seems like everyone likes to spawn new processes nowadays.

        Happy new year as well :)

    6. chafi says:

      thanks dear its very nice this methode

    7. Clive says:

      Thanks, man. One memory stealing process down. A dozen to go!

    8. Tracy says:

      Thank you so much for being a clever genius, this solution is wicked! I have been searching for a fix for days with an issue in Netflix- it freezes after I rewind or fast-forward (also in Chrome, but not IE). I found your post through a firefoxcrash blog and also shared it with my friends.

    9. Bob says:

      Fantastic. I used the second method. Worked great! Thank you so much for posting these instructions.

    10. Hamid says:

      Thanks mate, works well nice and clean instructions without any bs.

    11. JW Dant says:

      Do the plug ins still work after either method is used?

      • CooLMinE says:

        Yes, plugins are not affected in any way. The only difference, as explained to the first paragraph of this article, is that if a plugin crashes it will probably take Firefox down with it, whereas if plugin-container is enabled then plugin-container.exe will crash instead.

        • JW Dant says:

          OK. My trouble is more that many times after a Firefox crash then the box comes up that says plugin-container stopped working. After I’ve had to ctl-alt-del Task Manager my way out of Firefox

    12. JW Dant says:

      Haven’t yet. Thinking of doing it if it might make Firefox more stable on this machine.

      • CooLMinE says:

        Try the second method and see if that helps with the crashes (the first method isn’t working on the newest Firefox versions) .

        Worst case scenario if it is an unstable plugin causing the crashes, your Firefox will crash instead this time. In that case you can easily reverse the steps and switch back to the plugin container within a few seconds.

        Best case scenario it was a plugin conflicting with the sandbox environment of plugin container and the crashes will stop.

        But in general you have nothing to lose other than a couple minutes that it will take you to test it out, so you have nothing to worry about.

    13. JW Dant says:

      Disabled it the second way and working fine. Tried the trouble spot that blew it up this morning and all ok. Will keep advised. Thank you.

    14. edward says:

      My web site is not working all that well just wondering if this can be fix. please.

      • CooLMinE says:

        I will require a bit more information other than “is not working” to be able to help you.

        But in general, having the plugin-container disabled (or enabled) shouldn’t affect your website.

        The only reason it will affect a website is if you have a plugin installed that is conflicting with the website and it happens to conflict when in a separate process (plugin-container.exe).

        Other than the above (fairly small chance) scenario I don’t think disabling the plugin-container will fix your website, sorry.

    15. AJY says:

      Thanks. Method 2 worked like a “charm”. I owe you one.

    16. Tensys says:

      Thanks! This helped a lot. I was having trouble re-starting firefox quickly after closing it. It would take 8 seconds or so to relaunch when before it would load in a second or 2 at most. This second fix you listed not only fixed this issue but also just makes the browser in general a little quicker. Thanks again!

    Leave a Reply

    Your email address will not be published. Required fields are marked *

    CAPTCHA Image

    *

    You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code class="" title="" data-url=""> <del datetime=""> <em> <i> <q cite=""> <strike> <strong> <pre class="" title="" data-url=""> <span class="" title="" data-url="">