Firefox 48 arrives with multi-process support, drops old OS X versions and Android Gingerbread
Mozilla today launched Firefox 48 for Windows, Mac, Linux, and Android. The browser has gained multi-processor support (finally), enhanced protection against harmful downloads, and media improvements on Android.
Context & Ripple Effects
Firefox 48 lands at the tail of a steady release-train run: Firefox 40 brought Windows 10 support and expanded malware protection a year earlier, and Firefox 43 followed with a 64-bit Windows build and a stricter blocklist. What makes this release different is architectural — multi-process support has been Mozilla's long-delayed stability project, and shipping it marks the point where Firefox's internals start catching up to its release cadence.
The other half of the story is subtraction: dropping old OS X versions and Android Gingerbread trims the matrix of platforms Mozilla has to secure and test, a theme that recurs across this coverage.
First-order effects
- Users on pre-upgrade OS X machines and Gingerbread devices are cut off from future Firefox updates, forcing an OS/device upgrade or a browser switch, while desktop users get multi-process isolation that keeps a hung tab from freezing the whole browser.
- The enhanced harmful-download protection extends the malware-defense work Mozilla started with Firefox 40's expanded protection, directly changing what happens when users click risky downloads.
Second-order effects
- With multi-process as the new baseline, Mozilla's subsequent rendering work — the smoother rendering and JavaScript caching in Firefox 58 — builds on this architecture rather than replacing it, so the payoff compounds over later releases rather than arriving at once.
- Android's media improvements push Firefox's mobile presence toward richer playback, setting up the eventual engine-level rebuild with GeckoView in Firefox 79 instead of incremental patches to the old mobile stack.
Third-order effects
- If the pattern holds, browser vendors treat legacy-platform culling as routine maintenance — each drop shrinks the security-testing surface and concentrates engineering on architectures (multi-process, then dedicated mobile engines) that can carry privacy and performance features forward.
- A browser whose core is process-isolated is structurally positioned for whatever workload comes next — heavier web apps first, and eventually more agentic uses of the browser itself — because isolation boundaries are the prerequisite for both.
The trend: Browsers are shedding legacy platforms and re-architecting their cores — multi-process isolation today, dedicated mobile engines later — so that security and performance features land on fewer, cleaner foundations.