Re:Firefox 54: E10S-Multi, WebExtension APIs, CSS Clip-Path
by codebolt on Wednesday June 14, 2017 @06:05AM
(#14551660)
I don't understand what you people are seeing who make these performance complaints. I switched to Firefox last year because Chrome was giving me a lot issues (often hanging and crashing when I had many tabs/large pages open). So far Firefox has been working like a dream for me.
Re:Firefox 54: E10S-Multi, WebExtension APIs, CSS Clip-Path
by zzalpha on Wednesday June 14, 2017 @09:36PM
(#14557328)
I really wish I could agree.
On a core i7 with 16GB and a completely fresh Windows 10 install that has never had Firefox on it (so we can't blame an old profile on the machine), Firefox with a single plugin (Keefox) is noticeably slower than Chrome. Just logging into my Google account I saw surprising amounts of basic UI stuttering. Something like Inbox (which is admittedly a pig) loads slowly and scrolls sluggishly.
Chrome, by comparison, is responsive and snappy.
I wish it were different. I really want to like Firefox, but on this machine, with some very basic tests it's clear that, for me, it simply does not compare...
Re:Firefox 54: E10S-Multi, WebExtension APIs, CSS Clip-Path
by jovial_galileo on Sunday June 25, 2017 @05:28PM
(#14632296)
Some legacy addons are poorly written. Have you tried a fresh Firefox profile with only uBlock Origin on it?
Re:Firefox 54: E10S-Multi, WebExtension APIs, CSS Clip-Path
by Semaphor on Wednesday June 14, 2017 @10:41AM
(#14553057)
I've often read FF is faster, HN is one of the few places I see Chrome being called faster. Maybe it depends heavily on the number of tabs and which sites are loaded? For me FF, whenever I tried switching, was always way slower and prone to freezes. But then I have 32GB Ram, 5 tabs always open (pinned), between 3 to 20 extra tabs at the same time and quite the number of extensions.
Everyone still seeing poor performance in Firefox 54, I personally would recommend to do a Refresh: https://support.mozilla.org/en-US/kb/refresh-firefox-reset-a... because usually it is an old add-on or wierd setting that causes it. At least it was in my case, and after Refresh firefox was running very fast