User Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:90.0) Gecko/20100101 Firefox/90.0

Steps to reproduce:

Visit https://github.com/login

Actual results:

Firefox completely freezes and causes graphical glitch/artifact and a CPU core 100% in GitHub login site, being unable to login into GitHub, also "Windows application not responding" message appears.

The workaround is to disable Hardware Acceleration in Firefox options.
But it's very bad because without HW ACC, Firefox runs 2x slower and websites load 2x slower.

The bug does happen since 85 release and has not been fixed even in 90.0.2.
It has been enought of time waiting by me with a hope of the bug to be fixed in one of the next FF releases, but it did not happen, thus it's time to report this annoying bug.

Tried already on a fresh FF profile without addons as well but the bug is still here.
Tried updating my gpu nvidia drivers to the latest one but the bug is still here.

My specs: Windows 7 SP1 64, Aero on, FF 90.0.2

Expected results:

FF should visit https://github.com/login with no problems.

The Bugbug bot thinks this bug should belong to the 'Core::Graphics' component, and is moving the bug to that component. Please revert this change in case you think the bot is wrong.

OK, the bug occurs randomly, for ex:

• there are days when it keeps freezing all the time and I'm unable to login into GitHub
• there are days when it does not freeze and I can login into GitHub just fine
• there are days when sometimes it does freeze, but sometimes not...

ALSO, the bug occurs not only at GitHub login page:

• it occurs sometimes at other websites (but most often at GitHub login page)
• it occurs sometimes not only when visiting a website, but also while doing some Firefox GUI actions for ex. "Pressing Hamburger Menu Icon -> Help -> About Firefox"

MOREOVER:

• when the freeze occurs, the whole Firefox needs to be closed by pressing "X" button and restarted, unable to close just the affected tab
• I'm tired of this bug, I spent motnhs with it already having freezes so often, like every second day, if the bug won't be fixed I will have no other choice than to switch to a different browser...

BACKGROUND STORY:

• I have been a long time Firefox fan/user, have been using FF in pre-quantum era and have reported many performance/lagging/crash bugs to Bugzilla (I don't have the old nick anymore), and since FF Quantum has been released, FF became fast and stable browser, last few years without filling a single bug, no problems at all. But since FF 85 has been released and HW ACCELERATION got broken and cause the whole browser freeze/crash, it seems the bad times came back with FF...

Do you have any extensions installed? Have you tried with a clean, new profile? In particular, do you have any gfx preferences toggled?

As well, can you attach your "about:support" information?

These are not all freezes I record and attach, there is 2x more of them, but I can't upload every one because this would expose my privacy.

From Attachment 9234319 [details], GPU process seemed to be disabled. The Windows 7 SP1 PC might not have platform update.

• https://searchfox.org/mozilla-central/rev/3a8091d1c29473a0839ad7a5810028f41363fe2e/gfx/thebes/gfxWindowsPlatform.cpp#1443

GPU_PROCESS:
available by default
unavailable by env: GPU Process requires the Windows 7 Platform Update

Yeah, I'm already aware that some things are unavailable on Win 7 SP1, but does that mean the issue won't be fixed for Win7 SP1 and I have to fix it by myself by updating my Win 7 SP1? Moreover, some of the unavailable things say they require Win 10 or later:

WEBRENDER_DCOMP_PRESENT:
available by default
unavailable by env: Requires Windows 10 or later

Could this mean that Hardware Acceleration might be still broken even after updating Win 7 SP1 and I will be forced to switch from Win 7 to Win 10?

And what about these, will they get fixed after updating Win 7 SP1 or need to switch to Win 10 to fix them?:

available by default
unavailable by runtime: Failed to acquire a Direct2D 1.1 factory
D3D11_HW_ANGLE:

WEBRENDER_COMPOSITOR:
available by default
unavailable by runtime: No DirectComposition usage

You won't get DirectComposition on Win7, but that shouldn't matter. DirectComposition allows us to hand off some extra work to the Win10 system compositor, for extra performance and power savings, but if it's not available it should still work fine, just somewhat less efficiently than it could on Win10.

Ok, so the day before yesterday, afternoon, I installed Windows 7 Platform Update (had to restart PC after this as well) and both GPU_PROCESS and DIRECT2D became available, and so far Firefox did not hang, so most probably the issue is solved, I appreciate the quick help!

Thanks!