<< The Speed of JavaScript in SeaMonkey | The roads I take... | Data Manager Now Part of SeaMonkey! >>

Plugin Crash Protection in SeaMonkey!

Some of you might have heard of "Plugin Crash Protection" or "Out Of Process Plugins", a feature that made its Mozilla debut in Firefox 3.6.4 and runs browser plugins like Flash and Java in their own processes outside the browser process so that in case of a crash they don't take the whole browser with them.

Since today's nightly builds, this is available in SeaMonkey 2.1 as well. This means that you'll find "plugin-container" processes running when you're using the SeaMonkey browser, those are the processes in which the actual plugins run in. Also, it means that a crash in Flash code will not take down your browser or even mail component of SeaMonkey any more!

We'll make this feature, just like the faster JavaScript and the Data Manager, available for more wide-spread testing in early October in our first beta.

Happy browsing with SeaMonkey 2.1!

Entry written by KaiRo and posted on September 23rd, 2010 23:48 | Tags: Mozilla, SeaMonkey, SeaMonkey 2.1 | 3 comments | TrackBack

Comments

Author	Entry
Tony Mechelynck from Brussels, Belgium	Mozilla/5.0 (X11; Linux i686; rv:2.0b7pre) Gecko/20100923 Firefox/4.0b7pre SeaMonkey/2.1b1pre Build ID: 20100923004652 In about:config, I notice the following: dom.ipc.plugins.enabled default boolean true dom.ipc.plugins.enabled.libvlcplugin.so default boolean false dom.ipc.plugins.enabled.nppdf.so default boolean false I have no plugin named libvlcplugin.so, but nppdf.so is the Adobe Reader plugin. Does the above mean that all plugins will use OOPP except the PDF reader plugin? 2010-09-24 02:24
KaiRo Webmaster	Tony, yes, that's what it means. We are not setting those prefs in our own SeaMonkey files, so they must be getting set from elsewhere, though (no idea from where). 2010-09-24 17:00
Adrian Kalla from Germany	And you did it again Wow. Just yesterday I read in the notes from the last meeting, that it could be hard to enable this feature and today I read this great news! It's amazing how fast the suite is progressing now 2010-09-25 01:06

Author

Entry

Tony Mechelynck

from Brussels, Belgium

Mozilla/5.0 (X11; Linux i686; rv:2.0b7pre) Gecko/20100923 Firefox/4.0b7pre SeaMonkey/2.1b1pre
Build ID: 20100923004652

In about:config, I notice the following:



dom.ipc.plugins.enabled                  default   boolean   true

dom.ipc.plugins.enabled.libvlcplugin.so  default   boolean   false

dom.ipc.plugins.enabled.nppdf.so         default   boolean   false

I have no plugin named libvlcplugin.so, but nppdf.so is the Adobe Reader plugin. Does the above mean that all plugins will use OOPP except the PDF reader plugin?

2010-09-24 02:24

KaiRo

Webmaster

Tony, yes, that's what it means. We are not setting those prefs in our own SeaMonkey files, so they must be getting set from elsewhere, though (no idea from where).

2010-09-24 17:00

Adrian Kalla

from Germany

And you did it again

Wow. Just yesterday I read in the notes from the last meeting, that it could be hard to enable this feature and today I read this great news! It's amazing how fast the suite is progressing now

2010-09-25 01:06

Add comment