Firefox crashing after 108.01 install
I upgraded to 108.01 three days ago. It crashed 3 times in the next two days, accompanied by that popup you get informing you of the crash.
For years I've been using the extraction method of the executable to create a Firefox portable application. Upgrading only involves the install folder. The profile remains untouched, unaltered.
I had an incident of profile corruption a couple months ago, with basically Firefox launching with most features not working, i.e. toolbar buttons, toolbar menus, etc. Yesterday, for a short time, aside from two crashes, I had a similar experience with the buttons, but not quite the same. My default built in Firefox buttons worked, but my extension buttons didn't. I also noticed on a page that I regularly visit, Ublock origin wasn't doing it's regular job of blocking, and the Ublock button was non-responsive.
I'm also in the process of using the Brave Browser for the first time. The reason I'm posting this here about this subject, including a Brave experience, is that at the same time I was experiencing the Firefox erratic behavior, Brave was crashing as well; freezing; tabs not loading.
Considering the Brave tabs not loading, and the temporary Firefox Ublock origin failure, etc., I'm wondering if there might be something in common here? Maybe an internet connectivity issue at the time?
Усі відповіді (16)
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.
bp-1a9a0d2b-aabe-43f0-838f-710430221222
bp-8a50ae17-0d29-424a-ad91-d459f0221225
bp-e284ae66-a04f-4f24-acd9-1187a0221225
bp-bb4329dd-de22-48a5-a25c-f88590221225
bp-5ae96e69-b1af-4355-a500-ef2360221225
i ALSO HAVE BEEN HAVING A NIGHTMARE SINCE THE 108.01 UPDATE
Submitted Crash Reports Report ID Date Submitted bp-fcd5a4b6-c4be-481c-9efa-2c8940221227 27/12/2022, 16:54 bp-bdd1b7f9-d503-4303-8577-b50ba0221227 27/12/2022 bp-550161d4-dcce-48eb-8d48-c47220221227 27/12/2022 bp-0d2ff95b-9654-45f1-a292-e03930221227 27/12/2022 bp-9c1afa5a-4f4d-423b-9afe-cdaec0221227 27/12/2022 bp-98df76ec-f18b-44d9-871b-4d62b0221227 27/12/2022
Not only have I had crashes since that update, many webpages are not presenting as they normally do. Access to fields on the page do not function. All heck as broken loose since the update. All was fine before update.
I'm curious if there were any conclusions derived from those crash reports posted here.
I was also having some unidentified odd/erratic OS behavior at that accompanied these browser occurrences. I didn't know which might be causing which, If they could all be related, as in the question I raised about the possibility of an internet connection aspect.
Since then I ran a sfc /scannow, and dism om my Windows 10. As a result, three corrupted files were repaired, and I also updated 3 intel drivers.
Everything has been stable now for several days, OS, Firefox and Brave, but I'm still curious if there is anything else I need to know about what those crash reports indicated.
I thought everything was ok, but it happened again yesterday. I left the machine alone for a while, and when I came back. Other apps were affected as well, Brave Browser, device manager, word and windows explorer
bp-330d55e0-aef1-4cb4-81aa-ea23e0221230
Hi,
Can someone please refer me yo somewhere I can go to get answers for this crashing issue, interprerting these crash reports.
I had two more crashes yesterday, but only one was recorded
bp-87a0ed60-28ed-4ebd-9d8b-ce1f70230111 1/10/2023, 4:15 PM
bp-22d7cb4a-0091-4729-9418-aa7900230110 1/9/2023, 4:45 PM
bp-7524b8af-b1f7-4fc9-97aa-5fd330230110 1/9/2023, 5:06 PM
But it seems random. Might not happen for several days, then 2 days in a row
If there is nowhere to go for answers, can somebody just let us know so we can stop coming back here to check? Thanks
Looks like problem with clearing memory via JavaScript Garbage Collection (GC).
Start Firefox in Troubleshoot Mode to check if one of the extensions ("3-bar" menu button or Tools -> Add-ons -> Extensions) or if hardware acceleration or if userChrome.css/userContent.css is causing the problem.
- switch to the DEFAULT theme: "3-bar" menu button or Tools -> Add-ons -> Themes
- do NOT click the "Refresh Firefox" button on the Troubleshoot Mode start window
If you're running Win Pro, try Windows Sandbox to see if you have the same issues. https://www.howtogeek.com/399290/how-to-use-windows-10s-new-sandbox-to-safely-test-apps/ What security software are you running?
Змінено jonzn4SUSE
sbods said
i ALSO HAVE BEEN HAVING A NIGHTMARE SINCE THE 108.01 UPDATE Submitted Crash Reports Report ID Date Submitted bp-fcd5a4b6-c4be-481c-9efa-2c8940221227 27/12/2022, 16:54 bp-bdd1b7f9-d503-4303-8577-b50ba0221227 27/12/2022 bp-550161d4-dcce-48eb-8d48-c47220221227 27/12/2022 bp-0d2ff95b-9654-45f1-a292-e03930221227 27/12/2022 bp-9c1afa5a-4f4d-423b-9afe-cdaec0221227 27/12/2022 bp-98df76ec-f18b-44d9-871b-4d62b0221227 27/12/2022
Your reports are showing Win7 running Firefox Version 95.0.2?
I had some OS problems that affected Firefox, as well as the broken Firefox profile with the session file corruption
I restored an OS backup image that predated all the Firefox related problems. I was able to put together a working Firefox profile, so all the session corruption is taken care of. In general, with Firefox, things seem to be ok,, but it continues to crash occasionally, randomly, i.e. yesterday, so If we can't glean anything specific from the report, what ever measures we take can't be verfied.
bp-9b5b4f2b-31c1-4cd2-960f-436210230203
There was no crash the previous day, and it's been 24 hours since then with no crashes.
Firefox and Chrome were open and crashed at the same time, and according to the windows Reliability Monitor, Firefox itself crashed twice at the exact same time. What's also odd about that is about:crashes shows only the crash posted above.
I use Windows Defender.
Змінено noel_envode
Good work! If you have no further questions, please mark this issue resolved and have a good day. I would suggest you run more than 1 version of Firefox so that you data is not in just 1 browser. see screenshots
This report looks like an OOM (out of memory) report where not enough contiguous free memory is available, also low on available Page file.
- bp-9b5b4f2b-31c1-4cd2-960f-436210230203
Available Page File : 4,300,800 bytes (4.3 MB) Available Physical Memory : 2,862,137,344 bytes (2.86 GB) System Memory Use Percentage : 83
Do you let Windows handle the Page file automatically or have you set a fixed size for the Windows Page File ?
- Control Panel -> System -> Advanced -> Performance -> Settings
If you use a fixed size for the page file then try the automatic setting and let Windows handle the page file size automatically.
cor-el said
This report looks like an OOM (out of memory) report where not enough contiguous free memory is available, also low on available Page file.Is it possible that a extremely large amount of tabs could be a factor?
Змінено noel_envode
I know I mentioned something to this effect before, but does anyone experience Firefox and Chrome/Brave crashing when they are active at the same time.
Happens pretty regularly for me. Currently, when it comes to crashing behavior for both, pretty much happens when they are used at the same time.