In iOS Firefox crashed due to plugin-container
I followed instruction several time to uninstall and reload fresh and Firefox will not run, except in safe mode. This issue has happened once before and I solved it by reloading it fresh but this time I cannot get it to run.
الحل المُختار
Been out for the last 2 weeks. After several attempts to resolve the issue I all but gave up. On my return I inverently opened Firefox without realizing it and after a few minutes I realized I was on the program and it was working fine. After checking Firefox was updated to V101 so that indicates the problem started with V99 and got worse with V100. In short I now fine. Thanks for all your assistance.
Read this answer in context 👍 0All Replies (12)
I checked Addons in private mode and still Firefox will not load.
I Downloaded from Mozilla.org each time. Yes, all adding are all disabled and the program will not load properly so I cannot go to any sights nor go into Private Mode. I'm able to see and do everything in safe mode. The last time this happened was several months ago and I removed the program emptied the trash and downloaded a fresh program and it I was up and running. This time that procedure did not work. I am not having any issues with other programs.
After messing with the program in Safe mode there is one add on which is running in private mode I turned it off to disable it. When I restart the program it turns itself back on. I assume the program is a default.
Add-ons Search Detection in private viewing.
smartin322 said
After messing with the program in Safe mode there is one add on which is running in private mode I turned it off to disable it. When I restart the program it turns itself back on. I assume the program is a default. Add-ons Search Detection in private viewing.
“Add-ons Search Detection” is built into Firefox. (I see it listed in about:support under “Add-ons”.)
As for Firefox crashing, can you describe exactly what happens when you try to start Firefox in normal mode? If Firefox crashes in normal mode does it start in Firefox Troubleshoot mode? (This is not the same as macOS "Safe Mode"!).
While Firefox is running, can you find and post a crash report ID?
- Enter about:crashes in the Firefox address bar and press Enter/Return. A list of Submitted/Unsubmitted Crash Reports will appear.
- Copy a few of the 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.
More information and further troubleshooting steps can be found in the Troubleshoot Firefox crashes (closing or quitting unexpectedly) article.
bp-3ec49e84-1cc7-4f1d-956d-a13f70220524 and submitted a few days old.
Q. While Firefox is running, can you find and post a crash report ID? Needed to go to safe mode.
Q. As for Firefox crashing, can you describe exactly what happens when you try to start Firefox in normal mode? I have to double click Firefox which is in the Dock. It starts with a long delay (more than 45 seconds) to load. Once loaded I get a white screen and I can enter an address but nothing happens when I hit enter. I can also select from the dropdown menus some work most do not and can select a Bookmark again nothing happens. I can start Troubleshoot mode and it will start but will not reopen Firefox.
Your crash report bp-3ec49e84-1cc7-4f1d-956d-a13f70220524 shows Firefox version 99.
I'm not very good at reading crash reports. If no one else has another suggestion you could stat Firefox again using Troubleshoot mode or macOS Safe Mode (whichever works) and then try a Firefox update to the latest version, which is 100.0.2, in case it helps. See Update Firefox to the latest release.
Even though I loaded the updated version the issue persists Thanks for your assistance.
If you still have the problem after updating to 100.0.2 then you can try to disable fission if Fission currently is enabled to see if that has effect.
You can check the current Fission state on the "Help -> More Troubleshooting Information" (about:support) page (search for Fission).
You can control Fission via fission.autostart on the about:config page, true to enable and false to turn it off.
- about:config => fission.autostart = false
You can open the about:config page via the location/address bar. You can accept the warning and click "I accept the risk!" to continue.
There is a bug report attached to the crash report, but that got fixed for 99.0.
- 1747959 - Crash in [@ je_free | nssCKFWObject_Destroy | NSSCKFWC_FindObjects | builtinsC_FindObjects]
Thanks. cor-el. I checked Diagnose Firefox issues using Troubleshoot Mode and it says this under
More information (Advanced users):
In addition to disabling add-ons (extensions and themes) and turning off hardware acceleration, Firefox Troubleshoot Mode disables Site Isolation, the JavaScript Just-in-time (JIT) compiler and ignores the optional userContent.css and userChrome.css files (if present). The xulstore.json file, which saves customizations to window sizes, toolbar settings and controls, is also ignored; however, any changes stored in modified preferences remain in effect.
(EDIT: added rest of paragraph, for the record.)
smartin322, since Firefox works in Troubleshoot mode, try disabling the fission.autostart preference in the configuration editor (about:config page), like cor-el suggests ... which turns off Site Isolation (Fission):
- Start Firefox again in Troubleshoot Mode.
- In the address bar, type about:config and press the Enter/Return key.
- The about:config warning page may appear. Click Accept the Risk and Continue to continue to the about:config page.
- Find the fission.autostart preference and click the Toggle button to set it to false.
- Restart Firefox normally.
Modified
الحل المُختار
Been out for the last 2 weeks. After several attempts to resolve the issue I all but gave up. On my return I inverently opened Firefox without realizing it and after a few minutes I realized I was on the program and it was working fine. After checking Firefox was updated to V101 so that indicates the problem started with V99 and got worse with V100. In short I now fine. Thanks for all your assistance.
smartin322 said
Been out for the last 2 weeks. After several attempts to resolve the issue I all but gave up. On my return I inverently opened Firefox without realizing it and after a few minutes I realized I was on the program and it was working fine. After checking Firefox was updated to V101 so that indicates the problem started with V99 and got worse with V100. In short I now fine. Thanks for all your assistance.
Thanks for letting us know that Firefox updated to version 101 and is working now.