Safari/Chrome Really Slow

[dcardoso]

Deleting the plugins using the method on the website was what did the trick for me. Thanks!

I can confirm that the plugins are the culprit for the slowness when loading new links. It seems that the more plugins you have, and the bigger file size they have affects the time it takes for the page to start loading, so I assume Safari is somehow reloading/refreshing the plugins everytime a new link is requested.

You can find the plugins in the following folders:
~/Library/Internet Plug-ins/
/Library/Internet Plug-ins/

 

[vbctv]

It looks like Google is trying to fix the bug but it is Apple related but something Apple can't fix because it's a change in code.
https://bugs.chromium.org/p/chromiu...ck Component Status Owner Summary OS Modified

It looks like Apple sandboxed stuff again & the Chrome issue is related to Fonts. I don't know if they can fix Chrome on Sierra without messing up older OS's.

 

[Paradoxally]

It looks like Google is trying to fix the bug but it is Apple related but something Apple can't fix because it's a change in code.
https://bugs.chromium.org/p/chromium/issues/detail?id=619981&can=1&colspec=ID Pri M Stars ReleaseBlock Component Status Owner Summary OS Modified

It looks like Apple sandboxed stuff again & the Chrome issue is related to Fonts. I don't know if they can fix Chrome on Sierra without messing up older OS's.

They'll find a way. Either way, Chrome is trash nowadays and I'm glad Sierra gave me a good opportunity to switch back to Firefox.

 

[Zer0Byte]

Hi
I already patch Chromium to work on mac OS Sierra
i can confirm the bug is gone

if you cant wait for a chrome release you can use my custom patch
https://we.tl/USXjdLndSZ

 

[grinny11]

Hi
I already patch Chromium to work on mac OS Sierra
i can confirm the bug is gone

if you cant wait for a chrome release you can use my custom patch
https://we.tl/USXjdLndSZ

Tried using it, wouldn't stay logged in with google services.

 

[Zer0Byte]

Tried using it, wouldn't stay logged in with google services.

Sorry to hear that but the distribuition of the Google api key is not allowed.

the problem with the speed is solved?

 

[grinny11]

Yes. Seems like the problem is solved on it.

 

[krishmk]

Yes. Seems like the problem is solved on it.

Still dog slow and using high cpu/ram for just one tab.

 

[Paradoxally]

Still dog slow and using high cpu/ram for just one tab.

I'd advise you to go back to El Cap. Fix is not being merged to stable until 2nd week of July, and even Canary will only get it early July.

 

[krishmk]

I'd advise you to go back to El Cap. Fix is not being merged to stable until 2nd week of July, and even Canary will only get it early July.

We have so many browsers that are stable, why go back to el cap.. Using safari/firefox at the moment.

 

[Zer0Byte]

Still dog slow and using high cpu/ram for just one tab.

Hi did you download the custom chromium i put on a link before?

 

[RTG4869]

Safari is killing me! Whenever I click on a hyperlink in Safari it freezes for a second, the dreaded beachball appears and then it opens up. The issue however, is not there when I Command+click on a hyperlink. Anyone experiencing this?

 

[YBY211]

Safari is killing me! Whenever I click on a hyperlink in Safari it freezes for a second, the dreaded beachball appears and then it opens up. The issue however, is not there when I Command+click on a hyperlink. Anyone experiencing this?

I have the same issue. Overall my late 2015 MBP is very slow since I installed Sierra. I tried to reinstall Sierra but it didn't help. Using Chrome/Canary is a bit better and smoother. All MS Office products are very slow too!
Not sure what is causing the sluggish behavior. My hard drive is half empty. The memory is not being overused either.

 

[Paradoxally]

We have so many browsers that are stable, why go back to el cap.. Using safari/firefox at the moment.

Because Sierra is not stable. Crashes all over the place.

 

[vbctv]

There are a few reasons for this. Chrome explained it already in the bug report. WebKit changed earlier this year, Blink Fonts are re-acting bad because of this change which all Chromium based browsers use. This will be fixed in July. But with the webKit change , it's possible Safari wasn't updated correctly for this first beta. Plus Safari could be in debug mode because it's a beta. Firefox works perfect and faster than before. This will all be fixed in Beta 2 or later & Chrome will be fixed in July. We have to be patient. This is a first beta...

 

[vbctv]

Dev build released today includes fix, should be included in Chrome Beta release tomorrow or Friday. But the Chrome Dev build that was released today includes the fix.

I can personally confirm Chrome Dev Build works perfect and uses normal memory. It was all due to Apple Fonts that caused the issue. It was actually fixed in WebKit early this year but Google was unaware of the change. It actually causes less memory usage...

 

[Paradoxally]

Thanks @vbctv, I will upgrade to the dev build. Was on the beta channel.

 

[vbctv]

Beta channel has now been updated also & I can confirm is working perfectly. I even think it's working faster as before just like on Dev build... So macOS Sierra must have better memory compression.