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

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

  • 171 பதிலளிப்புகள்
  • 71 இந்த பிரச்னைகள் உள்ளது
  • Last reply by AnonymousUser

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?

தீர்வு தேர்ந்தெடுக்கப்பட்டது

If anyone wants to disable the plugin container, read this:

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.



Read this answer in context 👍 0

All Replies (20)

While it did slowly get better (finally loaded a movie on Hulu), my Flash plugin is still crashing FREQUENTLY on, and the overall picture quality of the videos I do get to work is horrendous. The FPS is choppy, and the picture is fuzzy. It's a far cry from what it was before the latest FF update.

'Upgraded' to FF 3.6.8, now all kinds of problems: Freezes; crashes; "plugin-container.exe has encountered a problem..."; Ebay pages a complete mess; etc. Moving to SeaMonkey till someone tries to fix that when it ain't broke too!

I have the same problem, with 3.6.8. Makes the browser completely unusable as it is crashing all the time. I can't believe it still hasn't been fixed - it's seriously making me think about going back to Internet Explorer

Again, just disable the crash protection container and all your woe's will go away, its not needed and is the cause of all the problems, follow the steps here:

No, it IS needed and is certainly not the cause of all the problems. Your problems MIGHT go away if you disable plugin isolation (they might not), but it will probably cause problems in future updates.

Don't be like those people who still use Firefox 1.5 because the add-ons they like don't work with supported up to date versions of Firefox.

lol no it really isnt needed, it wasnt needed before it was implemented and its certainly not needed now, it is the cause of the problems as disabling it is the only thing that fixed the issues with FF, I tried everything else including disabling all add'on's

Since its implementation the crash protection container has caused nothing but problems, hangups and slow downs, its not needed and needs to be removed.

Well, the truth of the matter is crashes have reduced by more than 50% in Firefox since the introduction of plugin isolation, and that's because the vast majority of Firefox crashes were due to Flash and other plugins crashing and taking Firefox along with them. It's certainly a needed fix and it's very welcome.

Now, I understand that it may have caused some problems for some people, but it is simply not true that all problems with Flash are due to plugin isolation. All in all, if flash or any other plugin is having problems with Firefox, it's Adobe's duty to fix it, not Mozilla's. Plugins are made for the browser, not the other way around.

And, of course, plugin isolation is working flawlessly for the overwhelming majority of users, and there are no known problems with it that would lead to something like this.

Again Im going to have to disagree here, to me crashes went up 50% since the implementation of the container, I have never had any problems with firefox until this was implemented and I think that is true for many people.

Ever since I disabled the container FF has been back to the old FF I knew and loved, its quick, responsive and has no slow downs, lock ups or crashes anymore, and everything including flash runs fine so whatever it was trying to prevent clearly wasnt a problem to begin with.

If there are ongoing issues with flash and other plugins then mozilla need's to work with the developers to resolve the issues instead of trying to police them with a method that will undoubtedly cause problems which, for myself and many others, outnumber the benefits.

I say keep FF lean and clean, its really starting to get bloated and its beginign to drive people away, if I didnt find chrome so un-appealing I would have already switched.

Well, a particular user's experience and what he thinks is a bit different from reality, most of the times.

Crashes were around 3, if I remember correctly. So there you go.

And yes, many people have problems with the plugin container, but many people have only one eye, many people are called Aphrodite and many people don't know how to speak their mother tongue. "Many" is a dangerous word. Firefox 3.6, the latest version, is used by about 250 to 300 million people. Can you imagine how it would be if all of them, or even the majority of them would have problems with Firefox? The kind of media reception, the kind of exposure, the kind of flood both here and at bugzilla?

Plus, Firefox 3.6.4 Lorenz, or in other words, plugin isolation, was tested by more than a million beta testers. Since then, multiple bug fixes have landed, but it's one thing to fix a problem with Firefox, it's whole different story to fix a problem with a plugin. And Mozilla cannot do that. Only the plugin's author can.

I believe you will, as you say, disagree with me, but, without wanting to fall into the ad verecundiam pit, there's a reason the heads of Mozilla Foundation studied and worked very hard to reach where they are now. Flash is buggy software. It crashes often. Not for everyone, but for a significant chunk of the users. It's not about "working with Flash's devs", it's about ensuring that Firefox isn't damaged by the bad practices of third party developers. Of course, that's not really fully achievable, but the community that develops Firefox does the best they can. Plugin isolation is just one of the steps in that direction.

mozzila.. fix the damn plugin container already! All the more reason to finally go with Chrome!

Again, just disable the silly container and all your woes will go away and your browser will run as nice as you remember it.

FF 3.68 - it just gets worse and worse ! Your about to lose me FF ! Your browser NOW OFFICIALLY IS CRAP !

Done all the recommended steps. Version 3.6.8

Please fix - Very frustrating

Jim M, what happened when you tried a new profile, exactly?

I can't go to almost any websites without this error happen! I love Firefox, but this flaw is making me nuts, I'm so close to use internet explorer! Fix this, Quick!

I still have the same problem!!! I disable all my plugins - Firefox is ok didnt't crash at all, (but a guy needs to watch some videos, or play some online games and we need some plugins for that, right) I enable one (anyone) of my plugins - Firefox crashes.

I use Firefox V 3.6.8, Windows 7 The first crash was like less than a week ago

If any plugin causes this problem and it isn't related to any one plugin in particular, then it's probably something else that's causing this. Check your antivirus/firewall/security suite settings for any incompatibility or something like that. It's possible that it's something else too, but only you can detect what it is. I predict creating a new profile (managing profiles) will lead to the same problems, but you may want to try it nonetheless. One thing's for sure: this is not Firefox normal behavior, so it's a bug triggered by something outside Firefox. If the new profile doesn't have the same problem, however, it's likely that there's something wrong with your profile. Please report back so we can work together, if that's the case.

I stated this some days ago: on W7, if you run FF as administrator, you don't have crashes at all. It seems to be a matter of permissions. But running any navigator as an administrator is a security hole. What do you thing about????

  1. 1
  2. 2
  3. 3
  4. 4
  5. 5
  6. 6
  7. 7
  8. 8
  9. 9