I’ve done some more testing and it doesn’t seem related to scrolling anymore, so I’ve updated the title.

I was able to reproduce the issue by opening a single browser tab/window to our GitHub issues page that was never scrolled and has no scrollbar. After leaving the window/tab open for ~5 minutes (and moving the mouse over the window a bit toward the end) the CPU core spiked and we were off to the races. The developer console showed zero output this time.

I’m not sure what is going on, but I assume some JS infinite loop?

Let me know if I can help diagnose further.

Are you using Dark Mode? I see there’s a similar report here: About perfomance

Thanks for the suggestion, but no I have not enabled dark mode. =/

Is there any more input on the matter I can give? Anything else I can do to help diagnose?
This is a daily/hourly annoyance I would love to avoid if possible.

I don’t really have anything to be honest. I am seeing a lot of reports of Waterfox not working with GitHub but unfortunately that is a Waterfox issue and not one of our own. Is that what you’re using?

I am using a Celeron processor, from the series of HP Stream 5 years ago. The Operating System is Windows 8.1. I’m using Google Chrome as the browser. I’m also checking the Task Manager from time to time just to see the stats. Together with GitHub (even if I’m using Dark Mode), GitHub Community, Facebook and Twitter, the stats is really good.

Maybe, it’s really your machine and the installed apps, not GitHub.

image1366×768 93.3 KB

canuckjacq, I am using Pale Moon, not Waterfox. What is the issue Waterfox has?

xdvrx1, you’re not using a standards compliant browser, so I’m not surprised you’re not having problems. It is most assuredly a combination of GitHub, and my standards compliant browser that is causing an issue. And if history is anything to go by, it is almost always the web site causing the issue, not the browser.
But the browser developers are available to help diagnose and fix the issue on either end if the GitHub developers would like to reach out to them on their forum. Or probably vise versa.

If you’d like to join the discussion on the Pale Moon forum, here is that link: Pale Moon (Linux) consuming 100% of CPU core, won't relinquish unless app closed. - Pale Moon forum

By the way, this does not happen on the Pale Moon browser on any of my four Windows 7 machines, only on this one Linux machine. So I’m sure that plays into it in some way.

By the way, this does not happen on the Pale Moon browser on any of my four Windows 7 machines, only on this one Linux machine. So I’m sure that plays into it in some way.

yup, that’s what I’m saying too, the machine itself is one factor so I posted my specifics

canuckjacq, I am using Pale Moon, not Waterfox. What is the issue Waterfox has?

I think (this is not my area of expertise) the lack of Web Components support is the big blocker. I suspect the polyfill add on is the same for both Waterfox Classic and Pale Moon since they’re both forked from older Firefox ESR.

The Pale Moon community probably knows better and there’s a thread here: PM 28.14.2 Github - Page 2 - Pale Moon forum

We do have a list of our supported browsers available for full feature compatibility.

Yes, you’re quite likely right the lack of WebComponents support in Pale Moon is the issue (or GitHub’s insistence on using WebComponents…). The polyfill add-on I’m using to even get GitHub to work at all in Pale Moon has been a life saver, as I would not be using GitHub without it.

That list of supported browsers reads like a nightmare, and building to those non-standards compliant browsers is not something this web developer would ever recommend. But I digress.

It seems I’ll either have to wait for GitHub to build and test against standards compliant browsers, or wait for Pale Moon to gain WebComponents capability natively, or live with this poor behavior, or start moving our shop away from GitHub.

Cheers!

It is possible this issue no longer exists. I’m not sure if GitHub is behaving better or what, but I’ve had a couple GitHub tabs open for a few days now and still have normal CPU usage. This would have been impossible before.