As a frequent /r/firefox visitor - while I do agree that Fx team should spend more time investigating this, I still have to note that this is not a bug or something ssimilar that can be easily reproduced.
I have late 2013 MPBr and 2014 iMac and never had any issues of a sort ever since quantum release. The only problem (performance wise) were videos on Youtube, but it seems to be fixed already. So it is there for some people and it is not for the others. With dfferent Macbooks\software\setups etc.
I'm also using Firefox on an underpowered Ubuntu machine and it works wonderfully there though (no HiDPI screen).
When I did research about it (about a year ago) it seemed the devs were considering retina macbooks with a non-default resolution as origin of the bug for some reason - I'm referring to the display setting that appears as "more space" in the regular OSX settings menu, not some arcane hidden configuration.
I regularly check back because I love the idea of using their open source, somewhat privacy-focused alternative to chrome, but it's been years and still not a fix in sight.
To me it seems that a large segment of users using the Retina screens (most people on the osx platform) has severe performance problems. Some people have no problems. And that is just the state of affairs.
The weird thing for me is that there is no official "issue" or information about the problems since so many experience it.
Seriously wanted to switch to Firefox after the browser-sign-in "feature" but the performance on my high-end 2018 macbook pro with 16gb ram was just abysmal (20 tabs open tops).
I'm using Tridactyl for navigation, so i just press 'b' (:buffer) and start typing tab title or whatever. In a moment I'm on the tab that I needed.
There are a few handfull addons for tab management available.
>know what’s on those tabs?
I was the one who opened them, of course I know what's on those tabs.
I rarely have more than 10 open at a time and sometimes completely forget what's there or why I opened it - I find uber-tabbing impressive and baffling in equal measure.
If you know what you're looking for, what does having it open (but probably knocked out of memory?) have over using search/URL autosuggest? Just a workflow thing, or is it faster?
I think of my tabs as my documents (the ones I'm working with today, this hour or even this very moment).
I prefer keeping those documents on my table, because this saves me some time\effort and just more convenient (subjectvly). So active tabs are the documents right in front of me and knocked out of memory ones are the ones I'm going to work with soon or needed for some sort of reference waiting their time in some sort of document organizer.
>I rarely have more than 10 open at a time and sometimes completely forget what's there or why I opened it
Well, I just have good memory :D It's part of the way schooling goes here in Russia I guess and maybe the upbringing. Memory training was just another daily routine. Sometimes it's really hard for me to believe that some people can't remember the plot or the characters from the book they read a year ago, while I still can quote a book I read 15 year ago.
In the end I guess everything goes down to what kind of processes influenced your brain development or something like that.
I typically have related tabs around the one I find. E.g. recently I researched some details about the python requests library, but haven't finished implementing it yet. I can go back to that group of tabs that's in a somewhat logical order. Autocomplete wouldn't have that, and also suggest links I've already discarded as not interesting.
I've tried a few times to replace this workflow with bookmark groups etc, but I never got that to work in a way I'm completely happy with, and making my own extension that does it exactly like I want it to would be an interesting project, but too much work for now.
What I find useful is a browser extension that lets me copy-paste a list of all URLs in a window with their titles, so at the end of a research session I can move the entire list quickly to a markdown file and save it with a few notes.
This doesn't really help with navigation when you have 100+ of them, but this structure maps to your internal memory organizer too. Sort of.
It's like orrganizing things you keep in your room\apartment - you may have LOTS of things and from a 3rd person point of view they may seem unorganized, but not for you - you put things according to your own logic and even if you forget the exact coorditanes of some item you still can find if quick enough because you know where you should look for it.
Would you be interested in help to profile the issue and file a detailed bug? This would help fix it.
What i don't get is that it's an unknown problem, many people have already filed bug reports on the tracker:
https://news.ycombinator.com/item?id=18626325
(also see several blog posts like: https://www.kamshin.com/2018/07/firefox-on-macos-insane-batt...)
I think it has to do with running the Macbook Pro at scaled resolution which is pretty much standard among devs on MB pro no? (otherwise you will have very little screen real estate).
I just created i Profile through the Gecko profiler once again but i don't know if that captures the CPU data? What external profiler do you use?
Profile here from Firefox nightly, 1 minute of scrolling around https://fs8.transfernow.net/download/5c0a9b99f98e/master/Fir...
----
Very non scientific test below that i need to external profiler to confirm:
Symptoms:
I get a hot computer when browsing / working normally
high CPU usage leading to
fans constantly running and battery drain
Doesn't happen in other browsers
Comparative methodology:
Open 20 tabs and scroll a bit up and down for 1 minute.
Check CPU usage in Activity monitor.
Check fan speed an temp.
Repeat in all major browsers.
Result:
Safari, Chrome and Opera the fans stays silent and i get moderate CPU usage.
Firefox the fans kick in quickly (also ran first to have a fair baseline temperature).
Do I understand correctly that you're checking CPU usage immediately after having scrolled up/down, or while scrolling up/down, right?
Apparently, there are already people working on that bug. If I understand things correctly, Firefox uses transparent windows, but transparent windows use lots of CPU on some macOS configurations, and this somehow wasn't detected during testing (I imagine that the computers used for testing didn't have these configurations).
If this is the same bug, as is likely, the bug is identified and developers are working on it: https://bugzilla.mozilla.org/show_bug.cgi?id=1429522 . If you wish, you may leave a message on that bug mentioning that you are available for profiling and testing a fix.
It is my impression (but don't take my word on it) that the fix will ship in Firefox 65, which is currently in Nightly. Now, I'm not sure that the fix has already landed in the current Nightlies, but do you have the possibility of testing on Firefox Nightly if the problem is still present?
(usual caveat: Nightly has Telemetry activated by default – if you don't like Telemetry, don't forget to disable it)
Apparently, the bug is already identified, so this might not be necessary. More details in my answer here: https://news.ycombinator.com/item?id=18634165 .
If you wish, you may leave a message on https://bugzilla.mozilla.org/show_bug.cgi?id=1429522 mentioning that you are available for profiling and testing a fix.
I have periodically had firefox problems in performance on all platforms including the new Mac air I bought my wife, her old Mac Pro and various Ubuntu and Windows installations. As a general rule it is because I've kept it open for several days with lots of tabs with media in them running. I mean it's irritating but not an ongoing catastrophe that means I can't use. As I said in some other thread recently I have over the past 10 years I think had two occasions where FF performance was so bad I had to leave the platform for a some time until it was fixed.
I see a lot of people in this thread claiming problems, and I see a lot of people claiming no problems, and some like me in between. So I don't know what the statistical breakdown of performance complaints about FF in comparison to all other issues (and if those complaints are actually likely to be related), but maybe it is not as great as you think it is?
Searching Google for "FF performance issues site:reddit.com" time span : last 24H, and off course there is a thread where the highest rated comment is someone saying FF is "laggy" on OSX :https://www.reddit.com/r/mac/comments/a3gk1k/macbook_air_201...
My guess would be most people have issues but most consumers don't know better. Some have no issues, and it seems that's the ones with older "non retina" displays.
Also slow is relative. If someone hasn't had an experience with a faster browser, then "slow" just feels normal. I had that after using Firefox for ~9 months. It just felt normal, and then got a bit slow and unusable after a while. After switching back to Chrome on Mac, it was like a breath of fresh air. I forgot what a responsive UI felt like.
"Yes we are aware that a certain percentage has severe performance problems on osx, we believe this has to do with the Retina displays blah blah" - instead it seems like no one from the dev group has been following this problem when you ask them. Despite weekly threads, just like the posts here on Hackernews in every FF thread.
Check my other post:
https://news.ycombinator.com/edit?id=18626325
This issue is all over the place.
I will admit it was too harshly written, the issues seems to only be on the osx platform and Firefox is great on all other platforms, but the issue has been detailed in their own tracker and subreddit for many years.
If the Mozilla devs aren't paying attention to and haven't remedied the problem you're experiencing, perhaps you're the edge case?
I just wrote that their support subreddit is filled with posts about performance on OSX, this thread in itself already has loads of posts with people complaining about it, and my post just is getting lots of upvotes - how is that an edge case? Also all Firefox threads on Hackernews has these posts, every single one.
As i said before i have been following this for years. You having a 2012 computer is 100% the edge case - not that there is anything wrong in that, i love keeping tech for as long as possible.
How so? It's the same processor (Ivy Bridge) and GPU combo (HD 4000 + GT 650M) as the first few revisions of the retina MBP models. The big difference is the display resolution (1680x1050 vs 2880x1800).
You're saying this problem goes back five years (2013). Whether or not the 2012 model is particularly common now, the guts were common in 2013 back when you claim to have seen the problem.
I've got a newer (still non-retina) iMac and have used a variety of retina machines for work and haven't seen any performance problems with FF either. Sure, if I run a bunch of flash based video players I can get the fans to go nuts but that's not a FF problem (the same thing happens if I use Chrome, flash is just an inefficient means of rendering video).
If the Mozilla devs haven't reproduced your complaint on a first class platform it's a pretty safe bet that you're doing something whacky whether or not you realize it.
We are not discussing if your computer is an edge case tech wise, but if it represents a "commonly used device" on the osx platform, ie, a device with a Retina display. In other words an edge case market wise.
Also another guy just wrote "Definitely not an edge case", about all his companys computers above me.
I don't get your point in trying to say we are "whacky" people because we say there is a problem. Once again read other FF threads on HN an these posts are in every one.
Basically you said the developers of a major browser, browser engine, programming language etc etc etc are all stupid because firefox doesn't work optimally on some subset of mac users machines. If this effects 1 in 1000 mac users this could be biting quite a few people certainly enough to inspire a lot of complaints and still effect a tiny portion of firefox users especially if firefox users are already underrepresented on macs due to historical poor showing.
If Macs are 9% of desktops/laptops and firefox users are around 10% then 0.9% of users are mac firefox users even given an even distribution of users or more realistically 0.5% of users.
If a bug effects in in 100 users its effecting then 0.005% of users. If it effects 1 in 1000 its effecting 0.0005% of users.
The prior posters statement about poor performance with scaling sounds interesting and importantly repeatable. If its the source of the challenge in question it seems like it would be great to submit a bug report.
Bugs that effect everyone are quickly fixed. Bugs that effect a small minority are more apt to slip through. This seems like a more satisfying conclusion than just assuming Mozilla hires morons for 6 figures.
Eleven people out of the thousands of people that use FF on a Mac daily? Perhaps it's not Mozilla that's wronged you.
I don't know why you're trying to deffend the idea that this bug is not a (relevant) thing. I'm not OP btw.
Why? Hand waving and tantrums don't mean that what OP is experiencing is representative of the state of Firefox on OSX. OP is positing that it's this ancient bug that Mozilla developers have just ignored because they're so awful/incompetent/lazy/whatever, but there's no way it would be problematic on hardware that dates back to the original problems.
It just smacks of frustrated user doing something out of the norm and falling prey to this idea that their own experiences are OBVIOUSLY representative of the norm.
Me? I'd guess that OP is doing something like running with a non-scaled display, running something else that's disabling the integrated GPU, running a poorly behaved corporate plugin or anti-virus, loading something so memory intensive the computer is swapping to disk, has a poorly behaved corporate font installed (or too many fonts), or something else along those lines. Basically something that seems normal to OP but is, in reality, not.
I've seen plenty of poor behavior from Firefox and from the Mozilla devs, but this idea that Firefox just performs poorly across the board on OSX (or some increasingly specific subset of OSX) seems very unlikely given how much focus Mozilla has been giving to performance as of late. More likely I expect there's just a very vocal minority.
I'm not making a judgement on Mozilla devs and their competency or work ethics, and I don't think OP is either, but the fact remains that the bug is there and I'd guess it's decently easy to replicate given that I've encountered it in the wild a lot. If it's one tenth as usual as my personal experience suggests it should be at the top of their backlog.
Plenty of things there could be edge cases. In fact the very first thing I thought of was resolution. Running a non-scaled retina display could definitely cause all sorts of problems as all of a sudden the browser is rendering a much bigger canvas.
> I'm not making a judgement on Mozilla devs and their competency or work ethics, and I don't think OP is either
OP is absolutely judging Mozilla employees and if that carried through to the bug reports I'm sure OP filed, well, that could definitely color the response from Mozilla.
Most people here are superusers, and i personally am a dev.
Off course i have tried everything possible, clean install, new profile, HW acc off, boot to safe mode etc. To insinuate that i have installed some weird plugin and even talked directly to the FF devs without trying basic troubleshooting or have some weird anti virus plugin installed is beyond weird.
I also wrote it's the same with all of my colleagues MB's (15 people).
So how is this a tantrum and a vocal insignificant minority of it comes up again and again and the post is sitting at the top with lots of people agreeing? (i know not everyone has the problem).
Your other points i don't get. Scaling should not be an issue as it's not an issue for any other apps - disabling the GPU by accident, what? All other software works fine. You shouldn't need a discrete GPU for browsing.
This issue is all over the place, here just from their own bugtracker only from the last 12 months (detailed from this post https://www.kamshin.com/2018/07/firefox-on-macos-insane-batt...):
https://bugzilla.mozilla.org/show_bug.cgi?id=1404042
https://bugzilla.mozilla.org/show_bug.cgi?id=1422090
https://bugzilla.mozilla.org/show_bug.cgi?id=1191965
https://bugzilla.mozilla.org/show_bug.cgi?id=1429522
And from their subreddit:
https://www.reddit.com/r/firefox/comments/7d6pc6/firefox_is_...
https://www.reddit.com/r/firefox/comments/7g6k9n/firefox_qua...
https://www.reddit.com/r/firefox/comments/8if1fs/anyone_else...
https://www.reddit.com/r/firefox/comments/763avh/firefox_qua...
https://www.reddit.com/r/firefox/comments/6wv0d9/why_is_fire...
And here the devs asks for help for once (and admit a problem):
https://www.reddit.com/r/firefox/comments/7g6k9n/firefox_qua...
Just searching for random posts from the last 24 hours on reddit r/mac and bingo:
https://www.reddit.com/r/mac/comments/a3gk1k/macbook_air_201...
and you can find many more:
That you suggest all of these hundreds of people are imbeciles with weird plugins is beyond disrespectful when so many of us has tried to help mozilla debugging to no effect and with little info in return. Most of us are devs or superusers - the issue has been detailed through many technical blog posts, and investigated by highly technical people thank you.
I don’t understand how that is a difficult conclusion to reach.
My retina macbook pro never had any issues with FF.
Any Sandy Bridge i7 from 2012 easily outperforms most odern laptops.
There is some progress made in performance per watt, but raw performance strongly decrease after the 39xx series.
1st step to trying to debug would be removing your old profile completely, maybe try to disable extensions and HW rendering acceleration
Also i am a dev - i have tried all possible options to remedy this issue. I even wrote that i talked to FF devs directly. Wouldn't it be weird if i hadn't tried basic techniques?
It's like there is this weird tribal thing going on where there is this passive aggressive attitude towards the people having problems like "you guys must be idiots" even though there is dozens of comments with anecdata about no one using FF at their companies because of performance issues.
A lot of people have issues, some don't - doesn't make the ones that do have them complete imbeciles.
Sometimes "why someone hasn't tried that" is less about being clueless and more about not assuming how much people know about things.
I can imagine someone at Mozilla going "how do we debug this" and failing to reproduce the problem (I run FF on two different Macs/OSX versions and it runs ok on both)
Maybe FF can add some telemetry or have a special debug version for those with the issue, but I see how it can be frustrating
Edge preserves my battery the best, however Edge is not practical to use, so Opera with the battery saving option is currently the best bet.
Firefox is still my main development browser though.
(I don't know the exact details, I have a vague recollection of pcwalton explaining it to me)
Since I switched to 2018 Macbook Pro Retina the issue is gone.
I tried switching completely a month ago for the third time.
Sadly absolutely nothing has happened in a 5 year time-span. The performance on my high-spec i7 Macbook Pro is abysmal. ( same across several company Macbooks ) The fans speed up constantly like they have done it for years. It's completely unusable for "professional" work or just regular multi tab browsing and drains the battery in no time.
Safari, Chrome, Opera, whatever, doesn't have these problems. I actually haven't experienced an application that feels so sluggish and unoptimised in OSX as Firefox. Something is seriously wrong and the dev group must not be prioritising it?
I checked their subreddit and loads of people are fleeing the Mac version, even on the newest nightly builds of quantum - seriously what the hell is going on? Why hasn't "the bug" or whatever been found or defined in clear termes in over 5 years?
The day the app works without serious CPU issues i will uninstall Chrome and go to Firefox, but the handling of this problem makes me worried about the dev groups competence.
When i talked to devs in the subreddit many of them were like "Hey, that sounds weird, should be better in the new nightly, are you sure it's not ..." - an absurd answer in the light of the constant stream of people saying this for years and years - even in this thread i see multiple people saying it's useless on OSX.
To the dev group: Get a Macbook (many devs use them), open Firefox, identify the problem - should have happened 5+ years ago.