Update 85.0.2 has a major glitch!!!
I set my options to notify me of upgrades to Firefox, and I do download and install them regularly. Not anymore. 85.0.2 caused a major problem. It would crash regularly with any redirect. Probably not using technical term, but as examples: 1) in yahoo mail reading email from local paper, click on read more and it crashed (never did before) 2) on my child's school website and click to view lunch menu - crash!!! Firefox became totally useless. Crash turns monitors black and then screen identifies crash, it will go back to the previous page, but just don't try to click on anything or crash again.
Fix: you can't "downgrade" or uninstall update - so I found a good "restore point" in Windows 10 that took me back to Firefox 84.0.2 (FYI 85.0 seemed to work, but I don't want any hassles). If you try to use Firefox after "restoring" it will still try to ask you to update to the newer version. So, you have to go into registry and disable the updates. Restart and presto, Firefox back to normal operation (the dreaded 85.0.2 is still downloaded, but it won't install or ask you to install it all the time).
I hope someone fixes this. I wish I knew more about computer programming and could help. I will wait for a good while before trying to update or install a newer version. It's a shame because I appreciate the security fixes. I LOVE Mozilla Firefox but this incident woke me up to the imperfect nature of this science.
由 tmund19 於 修改
所有回覆 (7)
This is my first post - strange you cannot delete a post from this forum.
由 tmund19 於 修改
We're sorry to hear that Firefox is crashing. In order to assist you better, please follow the steps below to provide us crash IDs to help us learn more about your crash.
The crash report is several pages of data. We need the report numbers to see the whole report.
- Enter about:crashes in the Firefox address bar and press Enter. A list of Submitted/Unsubmitted Crash Reports will appear, similar to the one shown below.
- Copy the 5 most recent Submitted Report IDs that start with bp- and then go back to your forum question and paste those IDs into the "Post a Reply" box.
Note: If a recent Report ID does not start with bp- click on it to submit the report.
(Please don't take a screenshot of your crashes, just copy and paste the IDs. The below image is just an example of what your Firefox screen should look like.)
Thank you for your help!
More information and further troubleshooting steps can be found in the Troubleshoot Firefox crashes (closing or quitting unexpectedly) article.
These Crash reports are submitted now, but they happened within a day or two of the first and only one submitted at the time of crash. {1) bp-05d4352d-fb54-47c5-a097-42c140210211 {2) bp-96e5c6fd-6118-4c32-8464-e66110210215 (3) bp-23271eef-103b-4a27-948c-2f9aa0210215 (4 )bp-9c8211a4-a4ff-4406-950a-0fa7b0210215 (5) bp-5dd5783e-cf6f-41ba-9df7-c9cb50210215 (6) bp-b07ccecf-c643-4823-9dca-337740210215 (7)bp-c4c7db71-82f6-4f5c-944d-e01820210215 (8) bp-3715c43f-ee61-4302-a9c6-8e1970210215 (9) bp-bcd82492-637e-4266-9a7f-c03a60210215
Obviously I submitted and copied more than five (9) - but I remember submitting one crash report so I submitted and copied the one's around that date and time. (1) is the one report I submitting at the time of crash.
Hope this helps. Thank you for answering me and taking the time out of your day
Product Firefox Release Channel release Version 85.0.2 Build ID 20210208133944 (2021-02-08)
Fri, 12 Feb 2021 01:57:00 GMT bp-96e5c6fd-6118-4c32-8464-e66110210215 Signature: OOM | large | mozalloc_abort | moz_xmalloc | mozilla::gfx::SourceSurfaceRawData::GuaranteePersistance
Uptime 4 seconds
MOZ_CRASH Reason (Sanitized) : MOZ_CRASH()
Crash Reason EXCEPTION_BREAKPOINT
This is for Sumo's Related Bugs 1683653 RESOLVED FIXED Crash in [@ OOM | large | mozalloc_abort | moz_xmalloc | mozilla::gfx::SourceSurfaceRawData::GuaranteePersistance] ++++++++++++++++++++++++++++++++++++++++++++++++++++++ Fri, 12 Feb 2021 01:55:18 GMT bp-23271eef-103b-4a27-948c-2f9aa0210215 Signature: OOM | small
Uptime 167 seconds (2 minutes and 47 seconds)
MOZ_CRASH Reason (Sanitized) : MOZ_CRASH()
Crash Reason EXCEPTION_BREAKPOINT ++++++++++++++++++++++++++++++++++++++++++++++++++ Thu, 11 Feb 2021 04:09:45 GMT bp-9c8211a4-a4ff-4406-950a-0fa7b0210215 Signature: OOM | unknown | NS_ABORT_OOM | XPCJSContext::NewXPCJSContext
Uptime 0 seconds
MOZ_CRASH Reason (Sanitized) : MOZ_CRASH(OOM)
Crash Reason EXCEPTION_BREAKPOINT
This is for Sumo's Related Bugs 1664308 NEW --- Crash in [@ OOM | unknown | NS_ABORT_OOM | XPCJSContext::NewXPCJSContext] ++++++++++++++++++++++++++++++++++++++++++++++++++++ Product Firefox Release Channel release Version 85.0 Build ID 20210118153634 (2021-01-18)
Thu, 11 Feb 2021 04:06:11 GMT bp-05d4352d-fb54-47c5-a097-42c140210211 Signature: RtlpAllocateHeapInternal
Uptime 65 seconds (1 minute and 5 seconds)
Crash Reason EXCEPTION_STACK_OVERFLOW
Basically, an OOM (Out Of Memory) means the system is having issues 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
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}
Thank you for your time: 1) I ran the windows memory diagnostic tool and had no errors. 2) I used HCI design's MemTest for awhile, but I don't want to leave my computer on overnight - I have 4 cores and so I opened and ran four tests of 1000MB each. At 50% complete on all four tests, I had zero errors. 3) I have 8GB of RAM and I can test again, but preliminary results seem to say I am ok.
Under Virtual Memory, I did/do have a custom size: Initial size 1920 - maximum size 4000. I toggled the "Automatically manage paging file size for all drives." I have plenty of space left on my 1TB hard drive.
Do you think that would cause the problem?
由 tmund19 於 修改
Watch for problems and we shall see.