Depending on how many browsers you have launched, it should show something like 1/1 (Enabled by user) or 2/2 (Enabled by user). To test this, open about:support and look for Multiprocess Windows. So tune that value to something your machine can take! If you spawn to many processes on a machine with just 2GB or 4GB of memory, you might run into swapping rather quickly!Īlso, you need to test this with your plugins and extensions! Not every plugin / extension will play nicely with e10s! In some cases the browser may even crash completely, or have individual tabs crash. You need to be a bit careful with however Each Firefox process might consume hundreds of megabytes, and with that property set to 16, Firefox can spawn a total of 17 processes, 1 master process and 16 child processes (=tabs). So force-enabling Electrolysis can only happen at your own risk! To enable the feature, open about:config, confirm the prompt, and then change the following properties as shown, create them manually if they don’t exist yet: trueī-enable trueĮxtensions.e10sBlockedByAddons falseĮxtensions.e10sBlocksEnabling false
Of course, this is not officially supported, not on XP / XP 圆4, nor on Vista. I’m happy to announce that it does work with Firefox 52.0 ESR though! This is a feature that makes Firefox more crash-proof and faster as well. I tried that before with some 50.x version and failed to have Firefox spawn multiple processes for multiple tabs. On top of that, I have reevaluated the functionality of Mozillas’ multiprocessing technology on Windows XP 圆4 Edition. That is, unless somebody provides patched builds, but I don’t think that’s gonna happen… Firefox 52.0 ESR reporting is version (Click to enlarge)Īccording to the, security updates will be provided for XP/Vista up until September 2017, and the actual, exact EOL date will be fixed mid-2017.Īfter that, there will no longer be any modern browser support for XP (NT 5.1), XP 圆4 & Server 2003 (NT 5.2) as well as Vista and the first edition of Server 2008 (NT 6.0).
0 kommentar(er)
