Very Frequent Crashes after MANY MANY Years of Beautiful Firefox Usage!
After using Firefox for MANY years, having an add Blocker installed and being smug how well it works, The last week has been so very tedious I'm at the point of frustration and thinking of an alternative browser. Firefox now has decided to crash Tabs or The complete Browser Often, Often when watching Youtube. Fixes Ive tried, Assign Page File to C:, Disable Add Blockers and tried another, Use Windows MEM diagnosis tool and no errors showed and Check Im using a none aggressive Mem clock = XMP Profile 1, Updated all drivers and GP software, GPU is at default clocks ( MSI GTX 970).
Heres a few reports for you to look over, Please drop ANY suggestions :)
43adbdc8-5d51-4379-9b73-87ef91b8715c 11/24/2021, 6:27 PM cd68bad1-bccb-4589-8c79-fa0ec81526e3 11/24/2021, 6:27 PM c274ab4f-fb40-48d8-b6ec-3b4b85482e3d 11/24/2021, 6:23 PM 26691bb1-28a1-4469-9392-b81fd7aea538 11/24/2021, 5:28 PM 5ce2fcef-6daf-4d93-ae09-985e1812dd30 11/24/2021, 4:47 PM 21ca0ccc-668f-43fc-adef-b386226498ca 11/24/2021, 4:23 PM
All Replies (8)
Those reports have not been submitted.
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.
Please, Do not post a screenshot ! !
For more help on crash reports, see; https://support.mozilla.org/en-US/kb/firefox-crashes-asking-support
bp-2746bacd-8329-40d8-b2d8-1f9900211124 11/24/2021, 5:50 PM View bp-30b516c1-c8ca-4250-9824-3de7b0211124 11/24/2021, 5:50 PM View bp-c533b3d0-d0b3-43c7-bf93-d727d0211124 11/24/2021, 5:50 PM View bp-a0b49143-8c3e-490a-8fd0-1b1690211124 11/24/2021, 5:50 PM View bp-1c477715-b027-4b99-bffc-944860211124 11/24/2021, 5:50 PM View bp-2b283010-c6d9-427f-b13f-0aafd0211124 11/24/2021, 5:50 PM View bp-9b7f63ff-d7c1-49f3-a9e9-6902b0211124 11/24/2021, 5:50 PM View bp-8a6f0d20-e703-4924-8491-a465e0211124 11/24/2021, 4:03 PM View bp-0465715c-7581-4726-971b-7cefa0211122 11/22/2021, 5:11 PM View bp-b5ec3730-c603-4e39-a649-3289f0211122 11/22/2021, 5:11 PM View bp-76501ca5-fafb-4883-85ab-1a6120211122 11/22/2021, 5:11 PM View bp-07931845-44b9-4386-add4-7f2530211122 11/22/2021, 5:11 PM View bp-bc949f6d-165c-4f18-a609-380480211122 11/22/2021, 5:11 PM View
Thanks, for some reason Some failed to submit
pppjhow32 said
Thanks, for some reason Some failed to submit
When a crash report fails to submit, it means the servers decided they don’t need that report.
About:Throttling “You're seeing this page because the crash report you selected was held back from submission. For statistical purposes, we don't need every crash report and sometimes we decline the submission of a crash report as a form of throttling." ++++++++++++++++++++++++++++++++++++++++++++++++++++ Bug 1662317 About Throttling Steps to reproduce:
My Firefox crashed but did not submit the crash report.
Actual results:
I tried to manually send the report, and the system gave me the message: About Throttling
Expected results:
If Mozilla does not need the report, I, the user, still want to know what happened. How else can I fix or understand what went wrong?
Product Firefox Release Channel release Version 94.0.2 Build ID 20211119140621 (2021-11-19)
bp-2746bacd-8329-40d8-b2d8-1f9900211124 Signature: je_free | mozilla::detail::RunnableMethodImpl<T>::~RunnableMethodImpl
Crash Reason EXCEPTION_ILLEGAL_INSTRUCTION ++++++++++++++++++++++++++++++++++++++++++++++ bp-30b516c1-c8ca-4250-9824-3de7b0211124 = Uptime 25 seconds Signature: js::jit::GetNativeDataPropertyPure
Crash Reason EXCEPTION_ILLEGAL_INSTRUCTION
This is for Sumo's Related Bugs 1706324 NEW --- Crash in [@ IPCError-browser | ShutDownKill | js::jit::GetNativeDataPropertyPure] ++++++++++++++++++++++++++++++++++++++++++++++++++++ bp-c533b3d0-d0b3-43c7-bf93-d727d0211124 bp-1c477715-b027-4b99-bffc-944860211124 = Uptime 136 seconds (2 minutes and 16 seconds)
Signature: RedBlackTree<T>::Remove
Crash Reason EXCEPTION_ACCESS_VIOLATION_READ
This is for Sumo's Related Bugs 1405062 NEW --- Crash in RedBlackTree<T>::Remove ++++++++++++++++++++++++++++++++++++++++++++++++++++++ bp-a0b49143-8c3e-490a-8fd0-1b1690211124 Signature: arena_t::MallocLarge | je_malloc | moz_xmalloc | IPC::Channel::ChannelImpl::OnIOCompleted
Crash Reason EXCEPTION_ACCESS_VIOLATION_READ ++++++++++++++++++++++++++++++++++++++++++++++++ bp-2b283010-c6d9-427f-b13f-0aafd0211124 Signature: mozilla::net::nsStandardURL::SetSpecWithEncoding
Crash Reason EXCEPTION_ACCESS_VIOLATION_WRITE
I called for more help.
Your crashes are all over the place. Sometimes this means there is a problem with the RAM.
https://support.mozilla.org/en-US/kb/firefox-slow-how-make-it-faster
https://support.mozilla.org/en-US/kb/firefox-uses-too-many-cpu-resources-how-fix
https://support.mozilla.org/en-US/kb/firefox-uses-too-much-memory-ram
https://support.mozilla.org/en-US/kb/firefox-hangs-or-not-responding
https://support.mozilla.org/en-US/kb/firefox-takes-long-time-start-up
https://support.mozilla.org/en-US/kb/quick-fixes-if-your-firefox-slows-down
https://support.mozilla.org/en-US/kb/firefox-uses-too-much-memory-or-cpu-resources
MemTest LAST UPDATED : 12/04/2020
Could you please run a tool from http://memtest.org/
in order to check the integrity of your RAM?
You will need a thumb or disk drive to install it on.
Do you let Windows handle the page file or did you set a fixed size ?
Control Panel -> System -> Advanced -> Performance -> Settings
If you use a fixed size for the page file then try the former and let Windows handle the page file. How to determine the appropriate page file size for 64-bit versions of Windows {web link}
Memtest came back PASS, no errors.
Im going to try and use your MEMORY related idea, Ive reset my BIOS and stuck with Optimized settings and C: has 16GB free so left PAGE file there, Tbh seems ok so far.
I appreciate your help and the time you've taken. fingers crossed
Not as Often, but still crashing...
Please post any new crash reports.