Firefox 55 adds support for in-browser VR
Mozilla's browser lets users tweak multi-process performance, takes another step nearer to kicking out FlashPrint
10 August 2017 | 0
Mozilla released Firefox 55 for Windows, macOS and Linux this week, debuting options to tweak the browser’s performance settings, adding support for the WebVR virtual reality standard and taking a major first step toward dispatching Flash.
Most users will likely find the new performance settings the most utilitarian of the feature updates. Building on Firefox 54, which used up to four processes to run the browser’s tabs, this week’s version lets individuals adjust that number, to as few as one process or as many as eight. The more processes assigned to tab content, the faster each will draw. The downside: The more processes, the more memory used by the browser.
The new setting can be found at Options (Windows) or Preferences (macOS) under the menu accessed from the three horizontal bars at the upper right. Uncheck the ‘Use recommended performance settings’ box in the Performance section.
Other additions, improvements and enhancements in Firefox 55 include support for WebVR (Windows only), the virtual reality-in-a-browser API (application programming interface) that originated at Mozilla but is also supported by rivals including Google (Chrome) and Microsoft (Edge). Firefox 55 also made click-to-run the default for Flash Player, a previously-announced step toward the eventual demise of the plug-in at the end of 2020; boasted a faster start-up time when restoring large numbers of tabs from the previous session; and let users select a search engine on the fly after typing a string into the address bar.
Mozilla patched 28 security vulnerabilities in the just-released version, five of them marked Critical, the firm’s highest ranking.
Firefox accounted for 12.3% of all browsers that personal computer users ran last month, a small increase from June and a 52% jump from July 2016, when the application seemed to be on the verge of vanishing.
The next edition, Firefox 56, should reach users 26 September according to the browser’s release calendar.
Mozilla in June continued its years-long campaign to make Firefox more technologically competitive with the competition, Google’s Chrome in particular, by boosting performance, increasing stability and reining in memory consumption.
The open-source developer also patched 31 security vulnerabilities, three of them rated ‘Critical’, the firm’s most serious ranking.
Firefox 54, released 13 June, expanded on Mozilla’s multi-process project, code-named Electrolysis (shortened to ‘e10s’), that since 2009 has tried to mimic Chrome, and separate the browser’s operation into more than one CPU process. Previously, Firefox split its user interface (UI) and all content into separate processes – running all tabs in one of those processes – to prevent the browser from completely crashing when a website or web app failed. Firefox 54 uses up to four processes to run the browser’s tabs, assigning each to one of the CPU buckets.
“By separating the tabs into separate processes, we make better use of the hardware on your computer, so Firefox can deliver you more of the web you love, with less waiting,” assured Nick Nguyen, the product lead for Firefox, in a post to a company blog. In the same piece, Nguyen bragged that version 54 was “the best release of Firefox ever”.
RAMing message home
Because operating multiple processes bloats a browser’s memory consumption, and also because Firefox pre-e10s was extensively criticised as a RAM pig, Nguyen asserted that version 54 uses “significantly less RAM” than rivals such as Chrome, Apple’s Safari and Microsoft’s Edge. Elsewhere, Ryan Pollack, a product marketing manager at Mozilla, argued that the four-process limit is the correct compromise between low and high memory use. He even cited the Goldilocks and the Three Bears fairy tale to declare that the balance between performance (lots of processes) and memory consumption (few processes) is perfect.
“Firefox uses four content processes because it’s the ‘just right’ number for many Firefox users,” said Pollack. “With four content processes, your computer should have plenty of memory left to run apps besides Firefox.”
Chrome has relied on a multi-process model since its 2008 launch. Because it devotes a separate process to each tab, and each process requires memory, Chrome generally consumes much more memory than other browsers. (Safari uses a similar, but not identical, multi-process model that ultimately eats less RAM than Chrome. Edge, too, uses multiple processes.) So, it wasn’t surprising that Pollack compared Firefox 54’s memory appetite primarily to Chrome’s, and charged that in a 30-tab test the latter required up to 2.4 times the RAM of Firefox.
Users with devices boasting larger amounts of RAM – more than 8Gb, Pollack said – can boost the number of processes Firefox 54 consumes by typing about:config in the browser’s address bar, then changing the number for the dom.ipc.processCount setting.
While e10s has been a focus of Mozilla engineers for two years, the project also illustrated how far Firefox had fallen behind other browsers, notably Chrome but even, in areas, Edge. Mozilla has suffered several massive defeats in recent years, including a drubbing over mobile operating systems and a lesser beating from a stab at in-browser advertising. Lately, it has rededicated itself to Firefox, but the jury remains undecided, with some, including a former CTO, maintaining that the browser has no chance of unseating Chrome.
Last month, Firefox accounted for 12% of all browsers used worldwide, about a fifth of the share owned by Chrome and half that of a combined Internet Explorer (IE) and Edge. That May number was the highest of the year so far, but it was also nearly identical to Firefox’s share of 24 months earlier, showing how mired the browser had become.
End users and IT administrators can download Firefox 54 for Windows, Mac and Linux from Mozilla’s website. Existing users’ browsers will be automatically upgraded.
IDG News Service