X
Tap here to go to the mobile version of the site.

Support Forum

I keep getting the following message and crash - "plugin container for firefox has stopped working." How can I fix this?

Posted

Over the last few day the interent has been crashing with the following response - "plugin container for firefox has stopped working." Why and how can I fix this issue?

Over the last few day the interent has been crashing with the following response - "plugin container for firefox has stopped working." Why and how can I fix this issue?

Chosen solution

If anyone wants to disable the plugin container, read this: http://support.mozilla.com/en-US/kb/The%20Adobe%20Flash%20plugin%20has%20crashed#Disable_hang_protection


Note that the above referenced KB article is about disabling the timeout and not about disabling the container process. To disable the container process you need to sett all dom.ipc.plugins.enabled prefs to false.

See http://kb.mozillazine.org/Plugin-container_and_out-of-process_plugins

cor-el

Read this answer in context 0

Additional System Details

Installed Plug-ins

  • -npmnqmp 989898989877
  • Office Plugin for Netscape Navigator
  • np-mswmp
  • 6.0.11.3006
  • RealPlayer(tm) LiveConnect-Enabled Plug-In
  • RealJukebox Netscape Plugin
  • Adobe Shockwave for Director Netscape plug-in, version 10.3
  • The QuickTime Plugin allows you to view a wide variety of multimedia content in Web pages. For more information, visit the QuickTime Web site.
  • Adobe PDF Plug-In For Firefox and Netscape "9.3.2"
  • NPRuntime Script Plug-in Library for Java(TM) Deploy
  • Default Plug-in
  • Provides additional functionality on Facebook. See our web site for details.
  • Shockwave Flash 10.0 r45
  • iTunes Detector Plug-in
  • 4.0.50524.0
  • Rhapsody Player Engine Plugin
  • Java(TM) Platform SE binary
  • Next Generation Java Plug-in 1.6.0_20 for Mozilla browsers

Application

  • User Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.2.4) Gecko/20100611 Firefox/3.6.4 (.NET CLR 3.5.30729)

More Information

Question owner

I AM the administrator and it didn't care...

I AM the administrator and it didn't care...

Question owner

This is what I mean (look at the screenshot)

This is what I mean (look at the screenshot)

Question owner

This is downright pathetic. This crash issue has been plaguing me for a few weeks now. Why is it so hard to make flash work? Everything was fine before the last update. Mind you I will NOT be making the move to Chrome but I will be finding an alternative to Firefox. The fact that the only "solution" offered is to deactivate the "Plugin Conatiner" is a slap in the face and akin to cutting off the arm because you've broken a finger. I have trusted FF & Mozilla for years now and it has not let me down yet, but it is rather upsetting that a hotfix has not even been issued.

This is downright pathetic. This crash issue has been plaguing me for a few weeks now. Why is it so hard to make flash work? Everything was fine before the last update. Mind you I will NOT be making the move to Chrome but I will be finding an alternative to Firefox. The fact that the only "solution" offered is to deactivate the "Plugin Conatiner" is a slap in the face and akin to cutting off the arm because you've broken a finger. I have trusted FF & Mozilla for years now and it has not let me down yet, but it is rather upsetting that a hotfix has not even been issued.
Morbus 135 solutions 2340 answers

Meanwhile, you haven't tried to work with me to fix the issue, have you? Disabling plugin isolation is not the only solution. In fact, it may not even be a solution at all! However, it's possible that you need to ask someone else for the solution, if the problem doesn't come from Firefox. You may need to ask your Firewall's author for support, if it's the Firewall that's blocking Firefox, you may need to ask Adobe for support, if it's Flash that's causing an issue, and so on and so forth. But first, please try to work with me and I'll help you the best I know and can.

Meanwhile, you haven't tried to work with me to fix the issue, have you? Disabling plugin isolation is not the only solution. In fact, it may not even be a solution at all! However, it's possible that you need to ask someone else for the solution, if the problem doesn't come from Firefox. You may need to ask your Firewall's author for support, if it's the Firewall that's blocking Firefox, you may need to ask Adobe for support, if it's Flash that's causing an issue, and so on and so forth. But first, please try to work with me and I'll help you the best I know and can.

Question owner

Morbus: At job I run XP SP3 and FF3.5.x with almost the same plugins than on by notebook with W7 FF 3.6.8, with no crashes at all. Yesterday, FF auto upgraded to 3.6.8 and this morning I had the first Flash crash. There must be something buggy at the 3.6 that wasn't at previous versions.

Morbus: At job I run XP SP3 and FF3.5.x with almost the same plugins than on by notebook with W7 FF 3.6.8, with no crashes at all. Yesterday, FF auto upgraded to 3.6.8 and this morning I had the first Flash crash. There must be something buggy at the 3.6 that wasn't at previous versions.

Question owner

i have disabled the shockwave flash plugin and now firefox has stopped crashing

i have disabled the shockwave flash plugin and now firefox has stopped crashing

Question owner

but without flash it sucks :)

but without flash it sucks :)
Morbus 135 solutions 2340 answers

You shouldn't have to browse without Flash. But the fact that the problem goes away when you disable Flash is an indicative that there's some kind of problem with Flash. Please contact Adobe for support (the first think they'll tell you is to update it, so you may as well do that right away).

You shouldn't have to browse without Flash. But the fact that the problem goes away when you disable Flash is an indicative that there's some kind of problem with Flash. Please contact Adobe for support (the first think they'll tell you is to update it, so you may as well do that right away).

Question owner

What good is a 'Help' site that sends you to a forum where everyone is asking the same question? And how am I supposed to tell whether or not some random person posting answers in a forum knows what he or she is talking about? Why isn't MOZILLA providing solutions? Some 'support'!!! Mozilla doesn't care, they don't have to care; they're a corporation, and like every other corporation they can do as they please. So what if their sh*tty product destroys your PC? What are you going to do, sue? Good luck. Rotten b*stards!!!

What good is a 'Help' site that sends you to a forum where everyone is asking the same question? And how am I supposed to tell whether or not some random person posting answers in a forum knows what he or she is talking about? Why isn't MOZILLA providing solutions? Some 'support'!!! Mozilla doesn't care, they don't have to care; they're a corporation, and like every other corporation they can do as they please. So what if their sh*tty product destroys your PC? What are you going to do, sue? Good luck. Rotten b*stards!!!
Morbus 135 solutions 2340 answers

Please read this for clarification.

Also, the Mozilla Foundation, who develops Firefox, is an open source, non-profit, public service organization. It exists thanks to the help of the whole community.

Answering your question, "how am I supposed to tell whether or not some random person posting answers in a forum knows what he or she is talking about?", you're not. There are no guarantees, but all I can say is that all the help I provide is completely harmless and should help you fix your problems, if you follow it correctly. Whether you choose to believe me is up to you. It's very important, however, that you read Mozilla Public Licence (Firefox's EULA): here. You'll see that there are no guarantees.

Answering your question, "Why isn't MOZILLA providing solutions?", it's unclear whether you are referring to Mozilla Foundation or Mozilla Corporation. I'm assuming you mean Mozilla Foundation, who develop Firefox, so all I can say is that all contributors in this site are part of the Foundation, simply because they are giving their time to help other users. That's all I can say about the matter.

Please read [http://support.mozilla.com/en-US/kb/How+to+contribute#What_is_Firefox_Support_ this] for clarification. Also, the Mozilla Foundation, who develops Firefox, is an open source, non-profit, public service organization. It exists thanks to the help of the whole community. Answering your question, "how am I supposed to tell whether or not some random person posting answers in a forum knows what he or she is talking about?", you're not. There are no guarantees, but all I can say is that all the help I provide is completely harmless and should help you fix your problems, if you follow it correctly. Whether you choose to believe me is up to you. It's very important, however, that you read Mozilla Public Licence (Firefox's EULA): [http://www.mozilla.com/en-US/legal/eula/firefox-en.html here]. You'll see that there are no guarantees. Answering your question, "Why isn't MOZILLA providing solutions?", it's unclear whether you are referring to Mozilla Foundation or Mozilla Corporation. I'm assuming you mean Mozilla Foundation, who develop Firefox, so all I can say is that all contributors in this site are part of the Foundation, simply because they are giving their time to help other users. That's all I can say about the matter.
Noah_SUMO
  • Moderator
98 solutions 607 answers

Chosen Solution

If anyone wants to disable the plugin container, read this: http://support.mozilla.com/en-US/kb/The%20Adobe%20Flash%20plugin%20has%20crashed#Disable_hang_protection


Note that the above referenced KB article is about disabling the timeout and not about disabling the container process. To disable the container process you need to sett all dom.ipc.plugins.enabled prefs to false.

See http://kb.mozillazine.org/Plugin-container_and_out-of-process_plugins

cor-el

If anyone wants to disable the plugin container, read this: http://support.mozilla.com/en-US/kb/The%20Adobe%20Flash%20plugin%20has%20crashed#Disable_hang_protection ---- Note that the above referenced KB article is about disabling the timeout and not about disabling the container process. To disable the container process you need to sett all '''dom.ipc.plugins.enabled''' prefs to false. See http://kb.mozillazine.org/Plugin-container_and_out-of-process_plugins cor-el

Modified by cor-el