Mozilla Announces Project Fission, a Project To Add True Multi-Process Support To Firefox (zdnet.com)
An anonymous reader quotes a report from ZDNet: After a year of secret preparations, Mozilla has publicly announced plans today to implement a "site isolation" feature, which works by splitting Firefox code in isolated OS processes, on a per-domain (site) basis. The concept behind this feature isn't new, as it's already present in Chrome, since May 2018. Currently, Firefox comes with one process for the browser's user interface, and a few (two to ten) processes for the Firefox code that renders the websites. With Project Fission (as this was named), Firefox split processes will change, and a separate one will be created for each website a user is accessing. This separation will be so fine-grained that just like in Chrome, if there's an iframe on the page, that iframe will receive its own process as well, helping protect users from threat actors that hide malicious code inside iframes (HTML elements that load other websites inside the current website). This is the same approach Chrome has taken with its "Site Isolation."
Firefox: Hold my beer.
In other words, more like Chrome which means even more CPU and memory usage for little gain.
If people think they're not going to go down the same road and eventually gimp extensions as well, then they're naive.
That implies a lot of CSS violations.. it's kind of the opposite idea to absorb and isolate. Project Boron.
Yippy. Another fucking update
Turning more and more into Chrome. One day it will be what Chrome is today.
I don't understand why processes are being used to provide security. Can someone explain it in more detail? If there aren't any bugs in the code, then it shouldn't matter where anything is running because it won't be able to do anything it's not supposed to do. If there are bugs in the code, why wouldn't they be able to exploit them to communicate with the other processes and cause just as many issues? I would think spending time implementing a simpler thread pool with everything being task based would be a more secure design. The threading model would be less complex (so in theory less bugs and any bugs are easier to find) and easier/faster to implement so they'd be more time left over to find and fix other bugs. Furthermore, a thread pool would be far more scale-able and resource efficient.
...and we'll have some real choice for privacy after Google/Chromium's latest dick move to nerf all adblockers other than AdBlock Plus, the one they have bought a huge interest in so they can control it.
What you suggest is in fact being done. Servo is the project to rewrite Firefox's engine in Rust, a modern language focusing on provable thread safety through abstractions with zero runtime cost. Quantum is the project to replace parts of Firefox's engine written in C++ with the parts of Servo that are completed.
That should be it.
This will do nothing to properly isolate inter-site scripting attacks, it will increase memory footprint (less if you are on linux and have ksm(kernel samepage merging) running and the threads flagged as ksm compatible.), increase attack surface, and further complicate the already messy debugging firefox requires.
If we were to go back and fork from FF-ESR 38, 45, or 52, implement this process isolation on a per-window or per-tab basis, and have plugins tied to per-window or per-tab sessions, the security, speed, and usability would be the same or greater than this half baked idea, while also reducing the debugging complexity and the overhead of this plan. Just because Scroogle does things one way doesn't mean we all need to get fucked by them even when we're using a competitors product (And despite Mozilla's collusion and no doubt kickbacks for all these Chrome-like changes, they ARE still competition.)
Time for an Ada browser on an Ada OS.
Domestic spying is now "Benign Information Gathering"
How long until we have some HTML5/CSS/JS hardware accelerated chip to do the actual rendering and just pass the display information to a 'thin client'?
At some point it's going to be faster to x11 forwarding/VNC to a bigger machine somewhere else to handle the latest JS framework.
>> After a year of secret preparations,
Can someone help me square the "open" part of OSS with "a year of secret preparations" please?
I have to turn the multi-process thing to "one content thread" for best performance. More processes doesn't help, especially on really old machines with single-core CPUs. I want the Firefox devs to dogfood on a fucking VIA C7.
So now I’m going to have like 500-600 additional processes running on my box every day. Hrm.
Is that a real thing?
I know you're just trolling for the lulz but Firefox already supports multi-processing through threading. They're moving to processes to sandbox things because a web browser's entire function is to run code from unknown/untrusted sources. But cool reference to the hip programming language bro. When you need something that actually works written by people who understand the requirements and the system it's running on I'll be over with the other graybeards. // and don't forget to bring us another shitty six pack when you do.
See subject (doesn't run in a browser) & APK Hosts File Engine 2.0++ 64-bit for Linux/BSD h t t p : / / a p k . i t - m a t e . c o . u k / A P K H o s t s F i l e E n g i n e F o r L i n u x . z i p
Yields more security/speed/reliability/anonymity vs. any 1 solution (99% of threats use hostnames vs. IP address most firewalls use) more efficiently/FASTER + NATIVELY 4 less!
Vs. "Bolt on 'MoAr' illogic-logic" slowing u hosts speed u up 2 ways: Adblocks + Hardcode fav. sites u spend most time @ vs. competition w/ security bugs (DNS/AntiVir) + overheads slowing u (messagepass 'souled-out' to advertisers easily detected & blocked addons + firewall filtering drivers) & their complexity leads to exploit!
* ONLY 1 of its kind in GUI 4 Linux (soon 4 MacOS)!
APK
P.S.=> Protects vs. scripts/trackers (kernelmode faster vs. usermode slower NoScript vs. 3rd party script)/ads/DNS request tracking + redirect poisoned or downed DNS/botnets/malware download/malcript/email malicious payload
So instead of taking 100% of my CPU, Firefox will be able to take 500% or 1000% of my CPU (100% for every tab I have opened and Firefox is spinning on for some reason.)
And so instead of nearly crashing my machine by hogging resources, it most certainly will.
Please, Firefox devs, get the CPU and memory leaks, javascript wedging, etc., under control before splitting things into more processes (which will just further hide such performance/memory leaks for now.)
At least one might (supposedly?) be able to kill off rogue/misbehaving pages on a per-process basis. But again, a properly functioning/secure/stable browser wouldn't have that need in the first place.
Sigh. 15% market share vs. Chrome's 60%, I fear for FF's future. It's my main browser, and the last viable hope for any privacy or security on the web (unless you wholehearted trust google.)
Love many, trust a few, do harm to none.
Memory footprint is bad with Quantum. Never had my laptop swapping until I upgraded to Firefox Quantum.
However, there is a workaround:
Under Preferences -> Performance -> Content Process Limit, change it from 4 to 2 or 1.
The default is the number of cores in your CPU, and when I went from a 2 core laptop to a 4 core one, memory skyrocketed. Setting it back to 2 or 1 keeps it under control.
Also add the Auto Tab Discard Addon, and set it for 15 minutes.
2bits.com, Inc: Drupal, WordPress, and LAMP performance tuning.
Ugh. I'm so tired of Firefox suddenly taking up 100% of my