Firefox コミュニティフォーラム

1. Close Firefox (FF) with some tabs open 2. While FF is closed the websites are updated 3. Open Firefox, tabs reopen 4. Go to tabs

Expected: Tabs should the latest version of the website (ie the page has been refreshed)

Actual: Tabs are showing the old, previous (cached) versions of the website and not refreshing to show the latest

User has to manuall refresh each tab to see the latest version of the page

Are other people seeing this issue?

Hello. I'm afraid there has been a data breach from either Firefox or Lockwise.

I have passwords that are used only in local development virtual hosts accessed only from Firefox that are showing up in Google password alerts.

This is a bug report & fix I found.

Firefox x64 DE 130.0b1 (however, it is not specific to this version of FF.) AMD 3900X CPU (all hardware clocks default unless otherwise noted) AMD RX 6900XT Corsair HX-850 PSU Latest device and chipset drivers from AMD and the respective manufacturers, from their sites Gigabyte Aorus Master motherboard (rev 1) 32GB DDR4 system ram (4x8) stock clocked at 3733Mhz, default timings Windows 11 Build 22635.4005 (Insider's beta-channel build--problem and solution are not build specific, I found)

Problem description:

• Two-three months ago, my previously rock stable system began regular crashing events, every 2-4 days average, sometimes twice a day, sometimes once every 4 days.

• Kernel Error 41, and I spent inordinate amounts of time trying to trace the problem as you might imagine from PSU to device drivers, you name it.

• Finally dawned on me that the hard crashes did not occur when playing a game or when punishing the CPU in some computational tasks--nope, I realized that every time the system crashed I was online running Firefox.

• I got it in my head (through some reasoning I don't even recall) that possibly the CPU stop error that triggered the critical Kernel error and crashed the system was due to a multi-threading bug in my trusty browser!

• So, I checked out Mozilla bug reports and stumbled upon this Windows environment variable, MOZ_FORCE_DISABLE_E10S 1, which I decided to try. It has now been two solid weeks without another episode--not even 1--and while I am not whooping and cheering wildly, quite yet, I do believe the problem boils down to some sort of obscure Ff multi-threading bug! Something was locking up process threads between cores! So, I thought I'd report it! If this gets ID'ed and fixed I'll be happy to try it on at some point...;)