71–80 of 265 posts
Earlier quoted context omitted.
I reported it and they know what the problem is but it got marked as no-priority. Everytime there’s a new release I check if it’s solved and move back to Safari. Every release there are people complaining about it. I know I have been for 2 years now, but it falls on deaf ears.
Might be hardware related. Did you provide your HW profile in the bug report?
Earlier quoted context omitted.
I reported it and they know what the problem is but it got marked as no-priority. Everytime there’s a new release I check if it’s solved and move back to Safari. Every release there are people complaining about it. I know I have been for 2 years now, but it falls on deaf ears.
issue ref?
Earlier quoted context omitted.
Strangely, none of my coworkers seem to have problems. But every release seems to get worse; first it was terrible performance, then fonts in pages and the UI became blurry. This happens even on newly-installed MBPs, so it’s doesn’t seem like it could be related to anything I’ve done. And yet… coworkers don’t have problems.
Try a profile refresh
Earlier quoted context omitted.
Yeah, well they know what the problem is but it fails to get a high enough priority to get solved: https://bugzilla.mozilla.org/show_bug.cgi?id=1407536
I find this confusing: there is tons of discussion in the thread, and yet: > UNCONFIRMED > Votes: 0 votes
Earlier quoted context omitted.
Regardless who is technically at fault, the Firefox team is best placed to resolve the issue. It kind of surprises me that this is an issue at all. I was under the impression a large number of FF devs use Macbooks.
Yeah, well they know what the problem is but it fails to get a high enough priority to get solved: https://bugzilla.mozilla.org/show_bug.cgi?id=1407536
Earlier quoted context omitted.
Mozilla owns Pocket. They're not calling them Pocket Sponsored Stories to be cute. You, too, can now buy screen space in the premiere open-source browser: https://getpocket.com/sponsor I think it's a disgrace.
I wish someone with the time would start producing a "De-Mozilla'ed" fork a la Chromium. I think Firefox has gotten to that point, things like this and the Mr. Robot fiasco indicate the project needs to be saved from itself.
Unfortunately, looks like the CPU spikes are still a problem on OS X for me. I check this every time a new version is released as I'd love to make the switch from Chrome, but Firefox with one blank tab and no extensions uses more CPU than Chrome with 15 actual tabs. When I actually throw activity at Firefox it hogs the CPU even more. Here's hoping v61 addresses it.
I'm unsure if this is actually Firefox fault. I'm running Linux (arch and Ubuntu), Windows and macOS, and Firefox is only slow on macOS, while my macOS machine is the second most powerful machine I have. Running Firefox in a Ubuntu VM on macOS is faster than running it natively on macOS.
Don’t you think it’s more likely there is a bug in macOS-specific Firefox code?
Garbage collection was pretty terrible too. I managed to use up 4 GB of ram with ~10 tabs. In my normal (firefox fork) browser I run 300 active/loaded tabs and 700 'suspended' tabs for ~1k total and never get that high.
There's seemingly still a lot of work to be done before it's usable as a main browser.
Earlier quoted context omitted.
Mozilla owns Pocket. They're not calling them Pocket Sponsored Stories to be cute. You, too, can now buy screen space in the premiere open-source browser: https://getpocket.com/sponsor I think it's a disgrace.
I wish someone with the time would start producing a "De-Mozilla'ed" fork a la Chromium. I think Firefox has gotten to that point, things like this and the Mr. Robot fiasco indicate the project needs to be saved from itself.