Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Lolu chungechunge lwabekwa kunqolobane. Uyacelwa ubuze umbuzo omusha uma udinga usizo.

Random Unusual Freezing, Yet Not Unresponsive

  • 4 uphendule
  • 2 zinale nkinga
  • 1 view
  • Igcine ukuphendulwa ngu Asa Dotzler

more options

Hello,

I've recently encountered a curious issue with my Firefox browser (Firefox version 102.0, Windows 11 Insider Preview 10.0.25145.1011). At seemingly random times it will freeze for between two and five minutes (roughly). UI elements become completely unresponsive and the cursor does not update when moving over the browser window. The window will not minimize. Yet, Windows Task Manager does not report the application as being unresponsive. While never a common problem, any freezes in the past would eventually cause the Windows Task Manager to identify it as unresponsive.

I have disabled "recommended performance settings" and hardware acceleration to no avail. Everything seems perfectly normal immediately before and after the freezes, and I've yet to identify how I can trigger them. I do not recall having made any changes to my browser before the freezes started occurring, though multiple Windows updates have taken place since then. If I'm too impatient to wait I will end the Firefox processes via Windows Task Manager and restart it so I can return to my tabs without having cookies deleted. I have 13 plugins mainly covering privacy/security concerns. Is there some sort of debug tool I can engage to see what's occupying Firefox while it's frozen? I've just found the Firefox Task Manager, and will see if it can offer any additional information during/after the freezes.

Thanks, Logan

Hello, I've recently encountered a curious issue with my Firefox browser (Firefox version 102.0, Windows 11 Insider Preview 10.0.25145.1011). At seemingly random times it will freeze for between two and five minutes (roughly). UI elements become completely unresponsive and the cursor does not update when moving over the browser window. The window will not minimize. Yet, Windows Task Manager does not report the application as being unresponsive. While never a common problem, any freezes in the past would eventually cause the Windows Task Manager to identify it as unresponsive. I have disabled "recommended performance settings" and hardware acceleration to no avail. Everything seems perfectly normal immediately before and after the freezes, and I've yet to identify how I can trigger them. I do not recall having made any changes to my browser before the freezes started occurring, though multiple Windows updates have taken place since then. If I'm too impatient to wait I will end the Firefox processes via Windows Task Manager and restart it so I can return to my tabs without having cookies deleted. I have 13 plugins mainly covering privacy/security concerns. Is there some sort of debug tool I can engage to see what's occupying Firefox while it's frozen? I've just found the Firefox Task Manager, and will see if it can offer any additional information during/after the freezes. Thanks, Logan

All Replies (4)

more options

Since posting I have encountered this issue again twice, both with Firefox Task Manager open. It freezes along with the rest of the application, but afterwards shows an increased "Energy Impact" from every process, which quickly returns to normal.

more options

This still happens to me once every few hours or so while using the application. Does anyone have a link or a lead that could help me diagnose this further?

more options

I was having the same issues in Windows and openSUSE, but after updating to 102.0.1 I have not had any issues so far.

more options

Logan, it's possible what you're seeing is covered here: https://support.mozilla.org/en-US/kb/firefox-hangs-when-copying-suggested-actions-windows-11

Then again, I don't have enough information to say for sure. Figured it was worth noting in case that was your issue as there's a workaround and a fix coming.