Firefox Quantum keeps crashing multiple times since upgrading to 68.0.1
Since I upgraded to Firefox 68.0.1, the browser keeps crashing excessively; either just individual tabs crashing, or the entire application. I've updated all my add-ons and plugins, and disabled hardware acceleration in both Firefox and Flash Player. I've reduced my add-ons to just the ones I'm not willing to do without (I haven't actually added any add-ons since upgrading, in any event.
If the only solution is downgrading, then that's a problem, too, because Mozilla made it impossible to run a downgraded build of Firefox with the default profile. Even launching it from the Command Prompt as "Firefox.exe -p" allows me to select my default profile, but I stilll get stuck with the panel after that which demands I either make a new profile or exit Firefox.
Using "Firefox.exe -allow-downgrade" and "Firefox.exe -p -allow-downgrade" don't work, either.
Wybrane rozwiązanie
These crash reports are OOM (out-of-memory) crashes where not enough contiguous free memory is available. You can try to increase the size of the OS page file.
Total Virtual Memory : 140,737,488,224,256 bytes (140.74 TB) Available Virtual Memory : 138,530,001,178,624 bytes (138.53 TB) Available Page File : 225,280 bytes (225.28 KB) Available Physical Memory : 1,149,272,064 bytes (1.15 GB) System Memory Use Percentage : 86 OOM Allocation Size : 8,192 bytes (8.19 KB)
TotalPageFile : 10547552256 TotalPhysicalMemory : 8540577792 TotalVirtualMemory : 140737488224256
You have quite a few extensions installed, so it is quite possible that this is causing your memory problems. You can check the Firefox Task Manager (about:performance) and about:memory pages.
- https://support.mozilla.org/en-US/kb/task-manager-tabs-or-extensions-are-slowing-firefox
- https://support.mozilla.org/en-US/kb/firefox-uses-too-much-memory-ram
See also:
Przeczytaj tę odpowiedź w całym kontekście 👍 0Wszystkie odpowiedzi (9)
Start Firefox in Safe Mode {web link}
A small dialog should appear. Click Start In Safe Mode (not Refresh). Is the problem still there?
While still in Safe Mode,
In the address bar, type about:crashes<enter>. Note: If any reports do not have BP- in front of the numbers/letters, click it to submit them.
The crash report is several pages of data. We need the report numbers to see the whole report.
Using your mouse, mark the most recent 7 - 10 Submitted crash reports, and copy them. Now go to the reply box and paste them in.
For more help on crash reports, see; https://support.mozilla.org/en-US/kb/firefox-crashes-asking-support
Also, try to create a new 'test' profile. Is the problem still there?
Crash Reports
bp-4a4c3429-77a7-4535-9ad2-7b2450190811 2019-08-11, 12:42 a.m.
bp-478b0ab2-2167-4f23-af5e-f3f120190811 2019-08-11, 12:42 a.m.
bp-027ec98c-3dd5-4c22-baa6-e59740190811 2019-08-11, 12:42 a.m.
bp-321bbac1-816c-4a16-aada-bd78d0190811 2019-08-11, 12:42 a.m.
bp-69aa47ea-3fde-42d0-9011-9380f0190811 2019-08-11, 12:42 a.m.
bp-1d1284b9-a3f9-4cc3-bf43-cf0f60190811 2019-08-11, 12:42 a.m.
bp-ded889e9-4349-47aa-a894-709620190811 2019-08-11, 12:41 a.m.
A test profile doesn't really help me, since I want my default profile to work.
Actually, I had a new problem appear in test mode. A lot of online images gave me a broken image icon, even though the image worked just fine in regular mode, so I think that I'm safe in saying that Firefox 68.0.1 is completely and totally borked.
Is there any way to downgrade and not have Firefox absolutely refuse to use my default profile? No matter what I do, it keeps giving me the pane that says I have to make a new profile, and even when I do that, and then try to switch back to my default profile, it goes back to showing that frustrating "make a new profile" frame. Seriously; what the heck is wrong with letting US decide what we do and don't do with what's on our computer? This ridiculous "Nanny-ism" is straight-up offensive!
If you have issues with accessing a profile then try to rename/remove compatibility.ini in this profile folder with Firefox closed.
Wybrane rozwiązanie
These crash reports are OOM (out-of-memory) crashes where not enough contiguous free memory is available. You can try to increase the size of the OS page file.
Total Virtual Memory : 140,737,488,224,256 bytes (140.74 TB) Available Virtual Memory : 138,530,001,178,624 bytes (138.53 TB) Available Page File : 225,280 bytes (225.28 KB) Available Physical Memory : 1,149,272,064 bytes (1.15 GB) System Memory Use Percentage : 86 OOM Allocation Size : 8,192 bytes (8.19 KB)
TotalPageFile : 10547552256 TotalPhysicalMemory : 8540577792 TotalVirtualMemory : 140737488224256
You have quite a few extensions installed, so it is quite possible that this is causing your memory problems. You can check the Firefox Task Manager (about:performance) and about:memory pages.
- https://support.mozilla.org/en-US/kb/task-manager-tabs-or-extensions-are-slowing-firefox
- https://support.mozilla.org/en-US/kb/firefox-uses-too-much-memory-ram
See also:
Zmodyfikowany przez cor-el w dniu
Sat, 10 Aug 2019 23:22:16 GMT bp-4a4c3429-77a7-4535-9ad2-7b2450190811 Sat, 10 Aug 2019 09:13:37 GMT bp-478b0ab2-2167-4f23-af5e-f3f120190811
Signature: OOM | small
Crash Reason EXCEPTION_BREAKPOINT ++++++++++++++++++++++++++++++++++++++++++++++ Mon, 29 Jul 2019 23:13:27 GMT bp-027ec98c-3dd5-4c22-baa6-e59740190811 Signature: js::irregexp::ChoiceNode::Emit
Crash Reason EXCEPTION_ACCESS_VIOLATION_READ
FredMcD said
Sat, 10 Aug 2019 23:22:16 GMT bp-4a4c3429-77a7-4535-9ad2-7b2450190811 Sat, 10 Aug 2019 09:13:37 GMT bp-478b0ab2-2167-4f23-af5e-f3f120190811 Signature: OOM | small Crash Reason EXCEPTION_BREAKPOINT ++++++++++++++++++++++++++++++++++++++++++++++ Mon, 29 Jul 2019 23:13:27 GMT bp-027ec98c-3dd5-4c22-baa6-e59740190811 Signature: js::irregexp::ChoiceNode::Emit Crash Reason EXCEPTION_ACCESS_VIOLATION_READ
Explanation, please?
See cor-el's post.
My Solution is to deactivate "Enable DNS over HTTPS".
Before that, my firefox 68.0.2 and 68.0.1 keep crash.