Mozilla lays out multi-process Firefox engineering goals

Re:Mozilla lays out multi-process Firefox engineering goals by experimental on Monday July 18, 2011 @08:57AM (#2776076)

On the article - What Mozilla are doing first with Electrolysis is like WebKit2, rather than like Chrome which is almost-but-not-there-yet process per-domain which will come later. There was also some original research which went into Firefox 4 with per-compartment garbage collection.

They're also looking at a multi-threaded DOM in Rust.

In case anyone hasn't been keeping up with it, Flash was already sandboxed months ago, before Chrome implemented it (this is different from Out Of Process Plug-ins).

I recommend you disable the Google Updater plug-in which takes up memory and doesn't really do much of value considering it shouldn't be in Firefox in the first place. NoScript has a click-to-play for Flash built-in so if you're using Flashblock get rid of it because it conflicts with NoScript.

[ Parent | on HN ]

Re:Mozilla lays out multi-process Firefox engineering goals by evmar on Monday July 18, 2011 @11:11AM (#2776587)

Chrome's flag for sandboxing plugins dates back to before the code was open-sourced: http://src.chromium.org/viewvc/chrome/trunk/src/chrome/commo... (search for "safe-plugins"). The reason it was never on by default for Flash is that you can't sandbox Flash without breaking Flash functionality. How did Firefox solve this problem?

[ Parent | on HN ]

Re:Mozilla lays out multi-process Firefox engineering goals by mda on Monday July 18, 2011 @11:37AM (#2776687)

Are you sure that Firefox sandboxes Flash? Care to give a reference?

[ Parent | on HN ]