搜尋 Mozilla 技術支援網站

防止技術支援詐騙。我們絕對不會要求您撥打電話或發送簡訊,或是提供個人資訊。請用「回報濫用」功能回報可疑的行為。

Learn More

Firefox is becoming very annoying crashing consantly. TIme to switch browsers?

more options

FIrefox is crashing all the time and is becoming unusable I dont have this problem with microsoft. should have about 200 crash reports

FIrefox is crashing all the time and is becoming unusable I dont have this problem with microsoft. should have about 200 crash reports

所有回覆 (6)

more options

hello, please provide your latest few submitted crash reports -enter about:crashes into the location bar, copy the latest few report ids from there starting with bp- & paste them here into a forum reply. this will give us a better understanding what may be triggering those crashes.

more options

Not clear on what to do. None of my crash reports start with bp. Am I supposed to open them? I can't copy links. Report ID Date Crashed d787d41e-984f-4552-b5bf-f94e05507929 7/4/2018 10:13 PM cf6b5db8-5393-4cf0-9767-f2848c8b51bb 7/4/2018 10:12 PM 7da4f0ef-64b4-4e84-a0ad-30a5d864c6d4 7/4/2018 10:09 PM 14b0605f-f735-41c3-9cbe-21d3ff066781 7/4/2018 10:08 PM aaf7596e-6ee7-464d-b222-a54224072086 7/4/2018 12:08 PM

more options

Please click your crash reports to submit them, than copy the ID's, they should start with BP- now

more options

Note: The about:crashes pages lists the Submitted Reports below the Unsubmitted Reports. After submitting a few of your latest reports, you may need to reload the page and scroll down to that section.

more options

Submitted Crash Reports Report ID Date Submitted bp-c7772330-e614-4a1f-8cf2-993000180706 7/6/2018 9:03 AM bp-688a0a38-8373-4ec9-9d0b-a55ea0180706 7/6/2018 8:57 AM bp-b2f6f4a4-ad90-4481-b2b1-4d4bd0180706 7/6/2018 8:54 AM bp-ae5c5252-040b-454e-9e11-140ab0180705 7/4/2018 10:17 PM bp-1c735a2e-4f5a-41ae-ba33-287841180705 7/4/2018 10:17 PM bp-29344caf-0421-487d-ab36-cd8c91180705 7/4/2018 10:14 PM bp-e5bf4544-5cba-4c5a-870b-2737d1180705 7/4/2018 10:12 PM bp-d1e6e7c6-405e-4512-ba8f-408cd1180628 6/27/2018 10:32 PM bp-11eab927-5d5d-412a-8300-bda811180627 6/27/2018 5:36 PM bp-7016d2be-67eb-4e35-9515-efa1c1180627 6/27/2018 8:00 AM bp-bb62ab0c-fd7a-4164-b207-8f84d1180612 6/12/2018 1:26 PM bp-b24f8145-7f37-4a92-b2ea-2071f1180612 6/12/2018 7:48 AM bp-4cde42ea-8b3c-48d5-8bf9-d7ab71180605 6/5/2018 2:06 PM bp-11b6c522-47ac-4f21-925e-effeb1180605 6/5/2018 8:21 AM bp-c848f0f8-7c96-4996-ac6f-e8b4b1180604 6/4/2018 3:41 PM bp-a3181030-24db-4baf-ae9e-25dd81180530 5/29/2018 9:11 PM bp-27d63aef-b129-47a9-9062-994881180530 5/29/2018 9:10 PM

more options

Hi jamof, thank you for the reports.

The first report is related to an Intel graphics file, perhaps related to video acceleration. Since there is only one of these, I don't know whether it is part of the pattern or just a rare one-off.

The next six reports are Out-of-Memory errors, nearly all of which occurred within the first minute after startup. Perhaps Firefox was restoring a lot of tabs?

What's odd to me about these reports is how tiny the "Available Page File" space is relative to the "Available Physical Memory", for example, 4-6MB vs. 4GB. Page file space usually is much larger than physical memory, not much smaller. ?????

The next two reports after that were also Out-of-Memory errors but they occurred after a sustained period of browsing. These also exhibit the very low page file space issue.