I'm planning on moving back to chrome this weekend. No amount of privacy can make up for the disruption.
It did used to run out of memory for images, and the UI of Firefox (and just Firefox) would sometimes pause, but those issues are a couple of years back now.
I'd dig deeper. There's something odd in your machine configuration.
In current iteration I would say it's way more probable that the person who started this chain has an overall issue with PC performance outside of firefox.
1. https://trends.google.pl/trends/explore?date=today%205-y&q=F...
Not in my experience, Chrome on Linux sometimes freezes even while switching tabs for a sec or two, while Firefox is super smooth.
[0] the roadmap to get GPU support on WebRender for example -- but I guess in time we'll see how that turns out.
[1] one which I had a few issues was the multiprocess approach. That brought me some trouble at first but in the end got ironed out just fine.
It's on Windows 10, Nvidia GPU. Have tried the bucket list of things to solve this without any solution so far. It happens even with just two or three tabs open.
I believe it boils down to this unsolved bug, at least in my situation. I do need to profile it myself if I want to know for sure though: https://bugzilla.mozilla.org/show_bug.cgi?id=1501281
It only happens with Firefox, nothing else. All other games, programs, browsers, etc run without issue. Firefox is the only commonality that causes the freezes. If there are no Firefox processes open, the freeze does not occur.
Oddly, I see you're on macOS, where I also used Firefox- but I never had an issue there. Interesting, because it seems my experience is the reverse of that of most Firefox users.
I switched from Firefox to Chromium after some problems I ran into on a laptop. The experience wasn't great, but I was willing to live with most of the issues.
However, even after disabling all extensions, it still pegged my cpus and froze my machine, several times a day.
I moved back to Firefox. No amount of features was going to make up for that disruption.
Overall it is just a clunky experience. And I can't run stuff I'm working on because they don't support communication with MIDI devices (they've been talking about it for years)
I think a better solution for many of us is an un-Googled version of Chrome/Blink, such as Brave or maybe even Edge when it is ready. You CAN get the best of Chrome without the worst, and the more Google does these things, the more effort people will go to to make it easier to do so.
Yikes, still? That exact thing happening way too often—with like a half-dozen very normal tabs open, and when FF wasn't even in focus—was what drove me first to Chrome (where I could open a stupid number of heavy tabs and not see problems as bad as FF), then later to Safari (for the double-digit-percentage better battery life than Chrome) on my Macbooks, and that was... wow, probably 2010 or so.
Perhaps they could benefit from a bug report.
There's a plethora of 'how to stop Firefox from being a cpu hog' articles online, which suggests that this isn't uncommon behaviour, nor limited to a recent release.
- 10% of laptops/desktops are mac
- 5-10% or less run firefox on mac. If firefox has more problems on mac I wouldn't be surprised if firefox had less marketshare on mac than overall.
-Some unknown percentage have major issues, lets call it 1% since lots of people report firefox works fine for them on mac.
You could be facing issues faced by only 0.05%-0.5% of firefox users. If people who face such issues overwhelmingly choose not to bother to report them then they will never be corrected.
Beta testing is unlikely to ever find all possible issues that will be uncovered when a product is exposed to millions of users.
Obvious bugs that effect everyone are quickly fixed. What's left is often less obvious issues that effect a smaller portion of the user base.
My point? You lost me as a Firefox user in the past. And I have been an avid Netscape Navigator, Netscape Communicator, Mozilla SeaMonkey (first milestones) and Mozilla Phoenix/Firebird/Firefox user in the past (I even used Phoenix 0.1). The only other browser which I used with pleasure, is Opera (with Presto).
It's not just that. I don't want a homogeneous browser culture. I believe that is bad on the long term.
This is on macOS.
There's a common element here and I'm trying to put my finger on it. It rhymes with Scroogle.
Why is it that the only websites I have issues with (Firefox user) are Google properties?
Or maybe, unlike the rest of the sites, Google engineers don't bother to test stuff on Firefox?
Google properties have a history of having suboptimal code served to Firefox.
Google may not care about my privacy, but there are no alternatives.
If there is no good answer to that, then how would I get warned of a vulnerability so that I can switch temporarily to Chrome till the vulnerability is fixed in Chromium?