Several Nice Browsers for Windows XP

[ProxRocks]

i rename the plugin-container from an .exe extension to a .bak extension...

this is the same as DELETING it...
it's never loaded/executed because it can't be found by Firefox, Pale Moon, New Moon, Windows, Linux, etc...

the plugin-container was created several years ago...
it was publicly introduced with Firefox 3.6.4 [June 22, 2010]...
it was for the purpose of "crash protection"...

<excerpt>
Firefox 3.6.4 provides uninterrupted browsing for Windows and Linux users when there is a crash in the Adobe Flash, Apple Quicktime or Microsoft Silverlight plugins.

If a plugin crashes or freezes, it will not affect the rest of Firefox. You will be able to reload the page to restart the plugin and try again.
</excerpt>

this "crash protection" is the plugin-container.exe...

BUT it is MY experience that New Moon NEVER crashes -
never due to plugins running within the same process as New Moon...
never due to plugins running within the "container" process...

the PLUGINS are simply NOT crashing...
doesn't care which process "contains" them...


RATHER - what i get is the CONTAINER PROCESS crashing when i close New Moon with NO TABS OPEN, ie NO PLUGINS RUNNING...

so whichever TAB that was opened that "loaded" the plugin-container, when THAT tab is closed, the plugin-container should ALSO be shut down, IMO...

because if NO TABS are running ANY plugins, then why is the plugin-container STILL loaded in RAM?


at any rate, for the time being, i simply don't need the "crash protection" that plugin-container.exe is supposedly offering me because it is my experience that there are no crashes to protect me from but rather it is the "protection" that in-and-of-itself is CRASHING


edit:
additional reading -
http://kb.mozillazine.org/Plugin-contain..._and_Linux

i may end up trying the dom.ipc.plugins.enabled from true to false...
in conjunction with dom.ipc.plugins.timeoutSecs to -1...


update:
i tried the dom.ipc.plugins.enabled from true to false in conjuction with dom.ipc.plugins.timeoutSecs to -1 and i'm getting no plugin-container ever loading (i renamed it back to its normal name)... so this should be a better fix...