Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

plugin-container.exe makes my computer hang forever. i don't want my older pc to get overheated over this and bail out on me

  • 8 replies
  • 126 have this problem
  • 2 views
  • Last reply by cor-el

more options

plugin-container.exe is making my cpu get to 100% immediately i go online. i first thought i got a virus somewhere, but no virus scan could find it. only then i checked the cpu usage to see what makes it go crazy, and it's plugin-container.exe, a program i thought legit, else i would've searched and destroyed it. turns out i'm not the only one having this trouble so guys, please do something about it. in the mean time i'm going back to 3.6.3 and hoping you solve this soon.

This happened

Every time Firefox opened

== after the update to 3.6.6.

plugin-container.exe is making my cpu get to 100% immediately i go online. i first thought i got a virus somewhere, but no virus scan could find it. only then i checked the cpu usage to see what makes it go crazy, and it's plugin-container.exe, a program i thought legit, else i would've searched and destroyed it. turns out i'm not the only one having this trouble so guys, please do something about it. in the mean time i'm going back to 3.6.3 and hoping you solve this soon. == This happened == Every time Firefox opened == after the update to 3.6.6.

All Replies (8)

more options

I'm leaving firefox - it was good while it lasted - but i haven't time to sort this out. It wasn't broke, but by trying to fix it - they then broke it - ciao firefox

more options

I get a firefox error saying I already have an instance of firefox open, but I just loaded it. So I have to kill the process firefox and container-plugin and then restart Firefox again to get it to come up. I have 3.6.4 and XP.

more options

The plugin-container make my FF hang everytime. I need to use Chrome to see Flash or Silverlight now. If FF don't fix this problem or let me choose using the plugin-container or not. I will totally use Chrome and leave FF!!!

more options

deleted You have one problem with firefox and you whine and want to use another browser? No one cares, use another browser and get a virus, go right ahead. Go complain to someone who cares *lol*

derogatory comments like that aren't permitted in this forum - moderator - eh https://support.mozilla.com/en-US/kb/Forum+and+chat+rules+and+guidelines
more options

My version of Mozilla is 3.6.8 and I have my task manager always running for killing plugin-container.exe when my browser fails...

more options

this forum is just for listing problems, not for finding solutions. I, too, am getting tired of FF's many small but annoying problems. I would like to know where to get some answers, if not here at the MOZILLA FORUMS.

more options

I found the way to stop using plugin-container.exe from somewhere and it works.

Steps to stop plugin-container.exe process:

   * Open Firefox web browser.
   * Type about:config in the address bar and press Enter key.
   * A warning will appear. Ignore it and press the "I』ll be careful, I promise!" button.
   * In the Filter field type dom.ipc. Six preferences will appear for the filter dom.ipc.
   * Ignore first and last preferences. Toggle (double-click) each of the four remaining preferences to change the value from "true" to "false".

Explanation: The crash protection feature in Firefox 3.6 is enabled for certain plugins only. The four preferences that we modified here specifies four different out-of-process plugins. They are the the NPAPI test plugin, Adobe Flash, Apple QuickTime (Windows) and Microsoft Silverlight (Windows). These plugins are specified in a separate dom.ipc.plugins.enabled.<filename> preference by default is set to true. We can disable them by changing their value to false. And thus plugin-container.exe will not run. By default the preference dom.ipc.plugins.enabled is already set to "false". So, no need to touch it. The dom.ipc.plugins.timeoutSecs is also not important here as other values are false.