You don’t have to wait for Firefox 3.7 so that fallen plugins stop dropping the entire browser

As many will remember, one of the important advantages of the future version of Firefox 3.7 is to isolate each plug-in (for example, Adobe Flash, Apple Quicktime or Microsoft Silverlight) into a separate process. Thus, if the plugin fails (and the process collapses), then it will not affect the performance of the entire Firefox, but only cause (in the rectangular area corresponding to the plugin) a sorrowful inscription like this:



However, Firefox 3.7 will not appear soon (only the fourth alpha version of it exists now ), and the developers decided to transfer (backport) this long-awaited function (isolating plug-ins into separate processes) into the current stable version of the browser - in Firefox 3.6.
')
That will be done, starting with the version of Firefox 3.6.4. Right now, it is undergoing preliminary testing, which will be completed from day to day, and then Firefox version 3.6.4 will replace the previous version (Firefox 3.6.3) with an automatic update.

Details on http://www.mozilla.com/en-US/firefox/3.6.4/whatsnew/ you can read by yourself. In short, I’ll say: this will be the final result of the development of the very same Firefox build that was previously known to beta testers under the name Firefox Lorentz .

_{As for the upcoming Firefox 3.7, we love it not only for this: in addition to isolating plugins, there will also be input fields (<textarea>) stretched by readers, accelerated shutdown, and most importantly - js-ctypes - support for accessing from javascript (from Firefox extensions) to any ready-made C libraries (.DLL under Windows, .so under Linux).}