Live data from Hacker News

Multiprocess Firefox

developer.mozilla.org

41–50 of 171 posts

Re: Multiprocess Firefox

#41
post #14
post #2

Finally some movement on this! It really feels like an inferior experience in 2015 when your browser freezes from an unresponsive javascript in another tab.

Chromium circa 2008?

Yes. Exactly like that. Firefox is damn near a full decade behind the curve.

Re: Multiprocess Firefox

#42

Please please test battery life impact while implementing the Multi-process stuff. I had to move away from Chrome just on the battery life issue. I suspect (but cannot conclusively prove) that the multi-process crap that Chrome has just drains your battery much faster. And yes I am perfectly aware of the supposed fix in Chrome for the battery killing bug.

There's no inherent reason why multiprocess would have a significant impact on energy, it just adds a relatively small amount of extra context switching and marshalling to what is already a huge pile of the same (your desktop OS). When the system is idle, or a page is rendered, the difference shouldn't be measurable.

Re: Multiprocess Firefox

#43
post #2

Finally some movement on this! It really feels like an inferior experience in 2015 when your browser freezes from an unresponsive javascript in another tab.

Chrome crashes and freezes all the time too.

Re: Multiprocess Firefox

#45
post #14

Earlier quoted context omitted.

Chromium circa 2008?

Yes. Exactly like that. Firefox is damn near a full decade behind the curve.

Multiprocess isn't some magical panacea, its use is essentially to contain buggy code which shouldn't exist in the first place (this is true for its use as introducing extra security context for page content as well as its improvements to robustness against hangs). In both instances, a safer implementation language, or moving rendering and JS interpretation off the UI thread could be said to be far more elegant solutions. Mozilla is about a decade ahead of the curve here, with Rust and Servo providing both.

Re: Multiprocess Firefox

#46

The problem with e10s (Electrolysis, codename for multiprocess Firefox) is it's actually less concurrent and runs far worse than normal Firefox, at least currently. It's downright unusable.

It may have less performance for various reasons, but it can't be less concurrent by definition. Previously there was no concurrency.

Re: Multiprocess Firefox

#47

I really hope Mozilla keeps NoScript alive. .. Please help the maker get it ported to support Multiprocess Firefox.

Is NoScript really at risk? That would be a big deal.

Yea the creator is asking for funding to port. He is just waiting for Mozilla to deliver which they said the were going to do.

Re: Multiprocess Firefox

#48

I really hope Mozilla keeps NoScript alive. .. Please help the maker get it ported to support Multiprocess Firefox.

Is NoScript really at risk? That would be a big deal.

the creator or noscript is working on it and from what i've read mozilla is aware of the issues and doing what they can from their end to make it possible for him to make it compatable: https://bugzilla.mozilla.org/show_bug.cgi?id=1058542

Re: Multiprocess Firefox

#49

Please please test battery life impact while implementing the Multi-process stuff. I had to move away from Chrome just on the battery life issue. I suspect (but cannot conclusively prove) that the multi-process crap that Chrome has just drains your battery much faster. And yes I am perfectly aware of the supposed fix in Chrome for the battery killing bug.

Do you have data on Firefox using less battery? I thought the order for energy usage was Safari < Chrome < Firefox (but can't find anything to back that up either).

Re: Multiprocess Firefox

#50

For the first time in years, the other day, I left Firefox open overnight. I use a proxy at work for Firefox due to strict filtering on our primary connection. I was monitoring the amtrack debacle in Philadelphia. I came in the next day to an entirely unresponsive Firefox. I had purposely gone to the home page before leaving to avoid bashing the processing with the live stream. Still, after ~12 hours of being on the…

Just remember that anecdote != data and all that. My ff gets restarted in two cases - ff or kernel gets security patch. That sometimes means a month of no restarts. (With maybe 30+ tabs in different groups open)

Same here. I keep sessions open for months at a time, with heavy tab churning (some days I have 30 open, then I close 10, open 20 more, etc).
Post reply on HN