Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Firefox 60 released

mozilla.org

Post reply on HN
Print view View original

41–50 of 265 posts

Re: Firefox 60 released

#41

Post by mccr8 »

apazzolini wrote: post #9

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.

That sounds kind of like a known issue with scaled resolution on OSX. Unfortunately, it doesn't look like any progress has been made on it.

https://bugzilla.mozilla.org/show_bug.cgi?id=1404042

Re: Firefox 60 released

#42

Post by Panino »

> Applied Quantum CSS to render browser UI

I'm so excited about the future of Firefox. In addition to the above, OpenBSD is currently working on pledge support in FF. In a couple years FF could be simultaneously faster, more private and more secure than Chrome.

Re: Firefox 60 released

#43

Post by lwansbrough »

apazzolini wrote: post #9

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 was gonna submit a performance profile as a bug report, but the https://perf-html.io profiler doesn't work in FF60

Re: Firefox 60 released

#44

Post by Paul-ish »

diggan wrote: post #29
apazzolini wrote: post #9

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.

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.

Re: Firefox 60 released

#45

Post by spiderfarmer »

butz wrote: post #15
apazzolini wrote: post #9

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.

Have you reported this bug? It's all fine on the old OS X Mavericks.

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.

Re: Firefox 60 released

#46

Post by dralley »

stouset wrote: post #31
Kpourdeilami wrote: post #16

Earlier quoted context omitted.

It is borderline unusable on the most recent Macbook Pro and most recent version of OS X. Weird that it only seems to affect some people

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

Re: Firefox 60 released

#47

Post by spiderfarmer »

Paul-ish wrote: post #44
diggan wrote: post #29

Earlier quoted context omitted.

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.

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

Re: Firefox 60 released

#48

Post by spiderfarmer »

stouset wrote: post #31
Kpourdeilami wrote: post #16

Earlier quoted context omitted.

It is borderline unusable on the most recent Macbook Pro and most recent version of OS X. Weird that it only seems to affect some people

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.

A profile refresh is useless in this case.

Re: Firefox 60 released

#50

Post by Karunamon »

stonogo wrote: post #33
Karunamon wrote: post #24

Earlier quoted context omitted.

That's significantly more defensible (it has to search somewhere by default, and most engines are known by their logos, and Google is the only search engine worth a crap) than imposing paid sites on you by default.

No, they could innovate by making a web browser that browses the web. Search is a prime candidate for extension functionality.

I've no desire to go back to the days of per-vendor search plugins like we had back around IE7, and neither do most.
Post reply on HN