FF15 hangs whenever plugin-container.exe is loaded in memory
I need help. Since at least in v14 and now v15, FF hangs becoming unresponsive whenever plugin-container.exe is loaded in memory, as monitored with Process Explorer of SysInternals. This happens in FF with all plugins manually disabled and with no extensions, loaded in either "normal" or safe mode, even after having reset it to default state in about:support. (The unresponsiveness is not absolute, since every some 90 seconds there is a brief refresh of the screen as indicated by an acknowledging screen change due to a prior click or mouse motion. (In this quasi-frozen condition, FF slowly ramps up its memory usage while plugin-container keeps alternating between two smaller vales in Process Explorer.) After some 15-20+ minutes, plugin-container unloads itself and FF starts responding again. If I then visit a page that triggers the loading of plugin-container, the described problem develops once more. Blocking the loading of plugin-container (e.g.,renaming or moving it out or blocking it with the firewall) hangs FF. The solution for FF 3.6.6 for dom.ipc in about:config does not work in these versions.
Ironically, the Mozilla support page about "Firefox crashes when loading certain pages" (http://goo.gl/i02Xz) is a page that loads automatically plugin-container and hangs my machine, so I had to enter the forums by selecting a different problem.
This occurs in a Windows-7 machine with sufficient memory (1025 MB physical, 1025 MB virtual) and a lean configuration (monitored and enforced with Autoruns and Process Explorer), which runs very well other browsers such as Chrome, Opera o IE9. I have been using FF since its v2 and would hate to switch permanently to a different browser. Any informed advice on how to fix the problem (or disable the plugin- container in a working manner) would be much appreciated. TIA.
Ausgewählte Lösung
TO: christianberg
Adding this Windows environment variable is quite simple: right click My Computer ~> left click Properties ~> left click Advanced tab ~> left click Environment Variables. Then select New in the lower pane (System Variables, which are global) ; enter MOZ_DISABLE_OOP_PLUGINS in the name field and enter 1 in the value field. Click OK twice to save and exit.
To confirm the variable has been added, run CMD.EXE ; once you are in the DOS box, enter SET at the prompt and check that the variable is indeed listed and set to 1.
Also, consider installing the FF extension Flashblock to run only those Flash-based images you want. (For me, installing the Flash plugin but disabling it, has been a better option: Flash images are blocked unless I enable them by clicking on the disabled plugin warning [see attached JPG image]).
Diese Antwort im Kontext lesen 👍 3Alle Antworten (5)
Does this also happen if you boot the computer in Windows Safe mode with network support (press F8 on the boot screen) as a test?
I do not know. Will try it. (Good question; and a scary one too: since the crash still occurs with the Startup list cleared, if it does not happen in the OS' Safe Mode, then it would likely be a conflict with some code, such as an original DLL or driver, that was later modified by some application, and this will take a lot of time and effort to solve.) Thank you, cor-el.
BTW, since the dom.ipc.plugins.enabled==false alternative for the earlier FF versions using Plugin Contain does not seem to work in v 14 & 15, since plugin container continues to load in my machine even though I have toggled to false those configuration settings, do I take it that now Mozilla has closed to door to the OOPP alternative of running without the container (with tested and trusted extensions)?
Solved by blocking the loading of Plugin Container . . .
Searching in the bugzilla.mozilla.org site for text or attachments on bugs related to dom.ipc.plugins...., I encountered several references to a Windows environment variable MOZ_DISABLE_OOP_PLUGINS, for example in the patch at http://goo.gl/jYJKL. I then added this variable to the Windows 7 system environment of my machine setting it to 1. It works : FF15 no longer loads plugin container (and therefore does not hang) when visiting web pages that before froze the browser.NB : As I discovered shortly thereafter in googling this environment variable, this method of blocking the loading of plugin container was already reported 3 weeks ago by big_v in the Mozilla support forum, http://goo.gl/v7prA. Chapeau.
How did you do that? I've also disabled plugincontainer in dom.ipc.plugins.enabled== to false but it seems the plugincontainer still like to load as usual.
My machine is quite stronger than yours with quad cpu's and 8 gigs of ram so those freezing is less frequent for me but sites that are flash-ad heavy still makes my system go down to it's knees.
Ausgewählte Lösung
TO: christianberg
Adding this Windows environment variable is quite simple: right click My Computer ~> left click Properties ~> left click Advanced tab ~> left click Environment Variables. Then select New in the lower pane (System Variables, which are global) ; enter MOZ_DISABLE_OOP_PLUGINS in the name field and enter 1 in the value field. Click OK twice to save and exit.
To confirm the variable has been added, run CMD.EXE ; once you are in the DOS box, enter SET at the prompt and check that the variable is indeed listed and set to 1.
Also, consider installing the FF extension Flashblock to run only those Flash-based images you want. (For me, installing the Flash plugin but disabling it, has been a better option: Flash images are blocked unless I enable them by clicking on the disabled plugin warning [see attached JPG image]).
