Post
by Moonchild » 2012-11-13, 21:41
If the plugin container crashes, it normally means that the plugin itself has crashed (the plugin container doesn't actually do much). As far as I understand, Quake Live uses a customary gaming plugin to be played - that makes things a little more difficult.
It's quite possible that the plugin you use in particular doesn't like the fact that the plugin container, as part of the browser, is also an optimized
executable. This may have many different causes - all of them would fall under interoperability issues with the specific plugin. Games run in custom plugins to "play in browser" are notorious for these kinds of problems.
In the end, the plugin container itself is nothing more than what it actually is called: a container. It has very little code in it, itself. If the
container crashes, it means that the plugin that is running in it has crashed or rather has terminated in a way it shouldn't.
I've actually had someone else (back in 2011 at the time of Pale Moon 4) complain about the same plugin causing a crash when exiting the game - so it is not the most stable when run in Pale Moon. Since you are on Windows XP, there's also little else that is saved in case of an application crash like that, so it's hard to gather more data on this crashing behavior.
"Son, in life you do not fight battles because you expect to win, you fight them merely because they need to be fought." --
Snagglepuss
