4 ms·
Adding multi-process to a large project that was not designed for multi-process is an astronomical amount of work. And Firefox's approach has advantages over Ch
by sp332 12y ago
Adding multi-process to a large project that was not designed for multi-process is an astronomical amount of work. And Firefox's approach has advantages over Chrome's, so they're not simply playing catch-up.
- Karunamon 12y agoUnderstood, but I'm speaking from the viewpoint of a user, here. It's a massive annoyance for a crashed tab to annihilate the other 49. (And the session restore being activated is generally grounds for a smoke break, because your system will be tied up for a while...)
- sp332 12y agoBut the issue isn't ignored or back-burnered.
- Karunamon 12y agoThat was more directed at the F-ING SSL issue, but still, end of 2015 to have a feature that's considered standard nowadays and introduced 7 years ago? How much of the work that went into deprecating certs and removing obscure command line flags and setting up HTTP/2 (which isn't even really used by anyone yet) could have went into electrolysis?
- blfr 12y agoSPDY indicator[1] tells me that HTTP/2 is active on all Google properties, including YouTube. That's a nice chunk of the web right there. I agree with you on older bugs just lingering around. This is a serious issue for many open source projects. JWZ was complaining about it years ago[2]. My favourite example is the problem of putting the tabs at the bottom of the window in gnome-terminal[3], which has been reported over 12 ago, has a patch available posted in the bugzilla, and it's still not fixed. [1] https://addons.mozilla.org/en-US/firefox/addon/spdy-indicator/ https://addons.mozilla.org/en-US/firefox/addon/spdy-indicato... [2] http://www.jwz.org/doc/cadt.html http://www.jwz.org/doc/cadt.html [3] https://bugzilla.gnome.org/show_bug.cgi?id=75420 https://bugzilla.gnome.org/show_bug.cgi?id=75420
- mccr8 12y agoNone of it. The work on multiprocess Firefox is primarily an issue in the front end UI code (written in JS), and does not have much to do with networking or crypto. Another thing to keep in mind is that patch notes are a list of user-facing changes, not a breakdown of where the engineering effort went in a particular 5 week release cycle. Removing the command line flag probably took an engineer an hour or two to do. In the same time frame, I spent weeks analyzing and fixing a variety of leaks that only show up in multiprocess Firefox, but none of that shows up in the patch notes.
- agumonkey 12y agoSince 38a (previous nightly) electrolysis e10s is enable by defualt IIRC. That's the main reason I favor Firefox instead of Chromium these days, since I'd love to provide them with automatic user feedback as much as possible. Multithreading isolates from crashes half the time, but some times everything will go down. Also there seem to be concurrent issues and threading overhead, for mundane page loading can become very very sluggish.
- Ded7xSEoPKYNsDd 12y agoSession restore in Firefox has been lazy for a long time now (the tab only loads when you activate it). It doesn't take longer than loading a single page. How often do tabs crash for you? That's the real issue if you ask me. I'm on Nightly (with Electrolysis!) and the last crash was over 2 months ago.
- iopq 12y agoI have a crash probably every day. Usual culprit is Flash.
- deleted 12y ago[deleted]
- icebraining 12y agoThat's weird, since Flash runs on its own process (plugin-container). Is it actually crashing the whole browser?
- oblio 12y agoIt shouldn't. At least on Windows I've gotten used to killing the plugin container about once ever 2 days. Firefox itself crashes once per month, maybe less. Firefox = rock solid. Flash = porous rock, at best :)
- RyanMcGreal 12y agoI find when Flash (plugin-container) goes down, it takes both Firefox and Chrome down with it. Running Windows 7 at work.
- iopq 12y agoIt locks up the entire browser so I have to force kill it. I'm on Windows 7.
- msujaws 12y agoYou should go to about:support and use Refresh Firefox which will probably fix most of your crashes (outside of Flash-related ones which should only be affecting the plugin and not the browser).
- kevincrane 12y agoSpeaking as a different user, one who looks at the task manager a decent amount, I really appreciate not having 49 different Firefox processes. This is definitely an issue of personal preference as it's been debated back and forth here a good amount, so no side is really "right" regarding single process v. multi process, but I'm firmly in the former camp.
- pwr22 12y agoI'd rather they make the code more robust to make crashes unlikely enough that they can actually debug and fix them when they occur, rather than going multi-process as a band aid to make recovery easier on a user That said, it is easy to recover from simply by re-opening FF and you're right back where you were and I haven't had a total browser crash in a long time. I do experience lock up issues though
- pekk 12y agoThere are other users you probably don't represent.
- tshtf 12y agoChrome's first public release, which included multiprocess tabs, was on December 11, 2008. There has been more than enough time for Mozilla to catch up.
- dblohm7 12y agoThey didn't have an addon ecosystem to contend with back then.
- Millennium 12y agoNote the words "first public release". Not to knock Chrome's achievements in this area, but it's an inescapable fact that they did not have any previous architecture to migrate from. Taking any nontrivial program that has had years to assume a single-process architecture, and updating it to work in a multiprocess manner, is hard. It takes time to do properly.
- wbkang 12y agoEven Internet Explorer has been multi-process since IE8. All other browsers do it, except Firefox.
- WaltPurvis 12y agoWhich is one of the main reasons I still use Firefox.
- joshstrange 12y agoPlease explain this line of reasoning. As is it reads as "I still use Firefox because I like that 1 tab can bring down the the whole browser"
- sp332 12y agoChrome chews through a lot of resources on my machine. Firefox is a lot lighter. And I think it will still be lighter since they're targeting a 2-process model instead of Chrome's (let me count) 17 that it just launched on startup.
- joshstrange 12y agoThank you! That makes sense, I still think I'd rather have per-tab isolation but I was genuinely interested in why FF would be preferable in this use-case.
- mmebane 12y agoChrome is utterly unsuited to the use case of leaving hundreds of tabs open, which happens often to me, as I only bother updating/cleaning my bookmarks a couple of times a year. There's three main issues with Chrome: 1) Nothing I've found that works nearly as well as Tree Style Tab. 2) Chrome always reloads all tabs when the browser starts up. Firefox, at least with Session Manager, will only load old tabs when I activate them. 3) Chrome takes up way more memory. That's partly due to #2, but partly inherent in the multi-process model. The Chrome UI also gets weird under load. With Firefox, it's easy to tell when it's laggy. With Chrome, the UI seems asynchronous, but there's no consideration for actions taking a long time, so you can get the annoying feeling of clicking with nothing obvious happening.