Page 1 of 1

NYTimes using 100% CPU??

Posted: Wed Apr 19, 2017 4:34 pm
by Stephen Hart
Anyone else notice The New York Times website becoming unresponsive and using a huge amount of CPU?
In the last week or so, the Times web site has become a real pain. Sometimes I can't scroll, pizza wheels pop up frequently, and Activity monitor reports using 100% of CPU or more.
Quitting Safari doesn't help. Restarting doesn't help.

In Firefox, I see Firefox using 50% CPU when I'm viewing The New York Times, but scrolling the front page is better.

Re: NYTimes using 100% CPU??

Posted: Thu Apr 20, 2017 10:04 am
by Stephen Hart
I found a few mentions of this issue, going back years.
Of course, the top suggestions are clear all website data and reinstall your OS. Bleah!

But one suggested clearing the Reading List. That seems to have helped. Now I see the NYT web site at 15% CPU, not 100%, and no fans running. Maybe there was one item on the Reading List that was trying to load.

Re: NYTimes using 100% CPU??

Posted: Sat Apr 22, 2017 10:29 am
by Stephen Hart
Still no solution to this. But the plot thickens. Our other iMac, right next to mine, does not have this behavior. I compared every Safari setting, but nothing there helped either.
Again, this is just the New York Times. Even the Doonesbury page in the Washington Post, a resource hog if ever there was one, doesn't cause a spike in CPU usage.

I even went into my Library in the Finder and deleted any folders or files with Safari in the name. This did not affect the problem. Also, I deleted all cookies, with no good effect.

I did find another site that runs CPU up past 100%, Slate. (I rarely visit Slate.)

Re: NYTimes using 100% CPU??

Posted: Sat Apr 22, 2017 2:40 pm
by Stephen Hart
So here's something that seemed to work.
One thing that is always suggested if you have problems with sites is to look at any extensions you have installed. I have two, 1Password and Shortly. I've had both for years.
So I disabled both and NYT home page worked normally. I added 1Password back, and NYT home page still worked normally.
Then I went to enable Shortly and Safari warned me that it was not an extension from the Safari Extensions collection. Baffled—because of course I got Shortly from the Safari Extensions collection—I deleted Shortly and then added it back from the Safari Extensions page.
Now I have both extensions active again and the NYT home page works normally. At least for the moment.
Also, the image-heavy Slate page I was looking at works fine.

Perhaps Shortly got corrupted in some way. I did find that the extension had been rewritten in late 2015. You would think that Safari would keep up with that in some way.