plugin-container crash out at startup

[patrickjdempsey]

So I saw this again today. Again in both Firefox and SeaMonkey. Either one runs out of memory and crashes out. From then on, subsequent attempts to open either Firefox or SeaMonkey result in continuous crashes from plugin-container loading along with them, which causes the page file to max out instantly at 3.2G. Normally opening Firefox or SeaMonkey only appears to require about 500Mb of page file. Since there's about 60G of free space on three different drives on this machine, I've set each drive to the maximum page file 4096Mb to see if that helps. I'm still rather confused as to why crash recovery is forcing this huge amount of page file usage.

[Zerebralus]

I got several (sent) crashes to... caused by killing the flash plugin service under task manager ( I guess) cause after killing the procress the browser suddenly crashed with the crash sumitting windows and the option to start the browser a new.

[patrickjdempsey]

I can usually safely force-crash plugin-manager without causing a browser crash. Just not when plugin-container opens as part of the startup.

[patrickjdempsey]

Ever since increasing the page file I have not seen this problem again.