This site will have limited functionality while we undergo maintenance to improve your experience. If an article doesn't solve your issue and you want to ask a question, we have our support community waiting to help you at @FirefoxSupport on Twitter and/r/firefox on Reddit.

Buscar en Ayuda

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 for Firefox has stopped working

  • 4 respuestas
  • 115 tienen este problema
  • 2 visitas
  • Última respuesta de Ray

more options

I constantly get this error message "Plugin container for Firefox has stopped working". I tried updating all addons, then disabling some, but it didn't work. Yesterday I reinstalled Firefox and didn't install any addons, but today I keep getting the message again. The fault module is always "StackHash_2264".

I constantly get this error message "Plugin container for Firefox has stopped working". I tried updating all addons, then disabling some, but it didn't work. Yesterday I reinstalled Firefox and didn't install any addons, but today I keep getting the message again. The fault module is always "StackHash_2264".

Todas las respuestas (4)

more options

Hi,

For a start, you can try to Disable all the Plugins in Tools (Alt + T) > Add-ons and then Enable them one by one.

Plugins Update

Troubleshooting Plugins

Testing Plugins

more options

I disabled the logmein addin, then went into logmein to control a PC. Logmein then asks if i want to install the plugin. I said yes and installed their plugin again. Worked for the connection instance but failed Next time

Modificadas por martinpurdy el

more options

I have this exact problem. Only happens with Logmein. I don't want to disable the logmein plug-in as I can still use it after clicking OK about 5 times. I'm hoping someone can come up with a solution.

more options

I have the same problem and I am not using logmein plugin so it may be something else causing it and logmein just makes it happen more frequent. just a thought.