Avatar for Username

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.

Update to Firefox 85.0 64bit hanging on opening private windows under some circumstances

  • Akukho zimpendulo
  • 1 inale nkinga
  • 9 views
robert.kissel
robert.kissel
more options

I updated from the prior version to 85.0 (64 bit) today (Windows 7), and a new problem has shown up almost at once.

Under some circumstances, in particular, when I have one private window open on a King game that utilizes animation (in particular, https://www.king.com/game/candycrush ) and, while this is open, if I attempt to open a new private window, Mozilla Firefox HANGS altogether (doesn't crash--but shows an egg-timer and Windoze reports that it isn't responding).

I did ""NOT"" observe this in the prior version, or in any of the prior versions, but it seems to be something I can recreate pretty regularly, so it seems to be a bug which will probably show up when using other Web sites, as well, although, so far, this is the condition under which I've been able to reproduce the behavior.

I imagine it'll be fixed at some point, but have no idea how to bring this to the attention of a developer properly.

I updated from the prior version to 85.0 (64 bit) today (Windows 7), and a new problem has shown up almost at once. Under some circumstances, in particular, when I have one private window open on a King game that utilizes animation (in particular, https://www.king.com/game/candycrush ) and, while this is open, if I attempt to open a new private window, Mozilla Firefox '''HANGS''' altogether (doesn't crash--but shows an egg-timer and Windoze reports that it isn't responding). I did ""NOT"" observe this in the prior version, or in any of the prior versions, but it seems to be something I can recreate pretty regularly, so it seems to be a bug which will probably show up when using other Web sites, as well, although, so far, this is the condition under which I've been able to reproduce the behavior. I imagine it'll be fixed at some point, but have no idea how to bring this to the attention of a developer properly.