Søg i Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Læs mere

Firefox keep crashing every day without reason at any moment

  • 8 svar
  • 1 har dette problem
  • 3 visninger
  • Seneste svar af FredMcD

more options

From the last weeks, I have some issues with my Firefox. I have tabs crash with "oops, the tab crashed.." (like my screen but it's in french). If I let a video or a stream for example after 10 or 40minutes I can have this kind of crash.

Do you have any idea of the origins of this problem ? Thanks !

From the last weeks, I have some issues with my Firefox. I have tabs crash with "oops, the tab crashed.." (like my screen but it's in french). If I let a video or a stream for example after 10 or 40minutes I can have this kind of crash. Do you have any idea of the origins of this problem ? Thanks !
Vedhæftede skærmbilleder

Alle svar (8)

more options

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.

  1. 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.
  2. 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.)

Fx64Beta-aboutcrashes-unsubmitted

Thank you for your help!

More information and further troubleshooting steps can be found in the Troubleshoot Firefox crashes (closing or quitting unexpectedly) article.

more options

Note that this is merely a tab crash and nor a Firefox crash. With a tab crash no crash report is send and thus no crash data is available.

Anything about these crash issues in the Browser Console ?

more options

cor-el a écrit

Note that this is merely a tab crash and nor a Firefox crash. With a tab crash no crash report is send and thus no crash data is available. Anything about these crash issues in the Browser Console ?


Hey there,

Thanks for your answer. I just saw a crash after 20min of utilisation, I saw a list of problems from my extension Language Tool at the same minute of the tab crash. I'm turning off this extension it to see if it's the origin of the problem. But I didn't knew this console, thanks !

more options

Greetings! These crashes may be due to the system running out of RAM. if you are willing to test this theory, run the following steps in your spare time:

  1. Open Task manager then drag the window to the left side of the screen in order to "clip" it. (If you've never used Task Manager before, you may need to select "more details" when it opens)
  2. Open Firefox then do whatever makes a tab crash the fastest.
  3. Monitor the Firefox "memory" tab in Rask manager (Firefox on the side then go to the Memory column)

If the particular "box" turns red or orange before the crash, it may be due to the system limiting/running out of RAM. Also keep an eye out for the CPU and GPU columns as they may also be causing the problem. Thanks.

Ændret af Infinity__ den

more options

Seburo a écrit

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.
  1. 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.
  2. 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.)
Fx64Beta-aboutcrashes-unsubmitted
Thank you for your help! More information and further troubleshooting steps can be found in the Troubleshoot Firefox crashes (closing or quitting unexpectedly) article.


Hey ! Thanks for your help, this is the 5 last crashes reports :

https://crash-stats.mozilla.org/report/index/34aa6a54-2326-444f-8da5-bbf190220406 https://crash-stats.mozilla.org/report/index/fe62b176-d08a-40bb-913a-659170220406 https://crash-stats.mozilla.org/report/index/6437d8c4-a3cd-4639-9144-4d1e70220406 https://crash-stats.mozilla.org/report/index/7e1031a4-b270-4ff8-b46f-0c1f40220406 https://crash-stats.mozilla.org/report/index/77a1aba2-a0ec-45b1-9f47-6263a0220406

more options

This problem may be caused via a RAM issue or a GPU error. Try running Firefox in safe mode(For instructions on how, visit this website: https://support.mozilla.org/en-US/kb/diagnose-firefox-issues-using-troubleshoot-mode). Is the problem still there in Troubleshoot/Safe Mode? Crash reason: EXCEPTION_ACCESS_VIOLATION_READ

Ændret af Infinity__ den

more options

Product Firefox Release Channel release Version 98.0.2 Build ID 20220322144853 (2022-03-22) Buildhub data OS Windows 10 OS Version 10.0.19044

Mon, 04 Apr 2022 20:15:40 GMT bp-34aa6a54-2326-444f-8da5-bbf190220406 Signature: js::jit::GetPropIRGenerator::tryAttachStub

Crash Reason EXCEPTION_ACCESS_VIOLATION_READ

This is for Sumo's Related Bugs 1702010 NEW --- Crash in [@ js::jit::GetPropIRGenerator::tryAttachStub] +++++++++++++++++++++++++++++++++++++++++++++++++++++++ Tue, 05 Apr 2022 17:40:37 GMT bp-fe62b176-d08a-40bb-913a-659170220406 - Uptime 228 seconds (3 minutes and 48 seconds) Signature: TraceCallbackFunc::Trace

Crash Reason EXCEPTION_ACCESS_VIOLATION_READ

This is for Sumo's Related Bugs 1204909 NEW --- crash in TraceCallbackFunc::Trace(JS::Heap<T>*, char const*, void*) in nsJSArgArray +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Product Firefox Release Channel release Version 99.0 Build ID 20220330194208 (2022-03-30)

bp-6437d8c4-a3cd-4639-9144-4d1e70220406 - Uptime 647 seconds (10 minutes and 47 seconds) Signature: mozilla::CycleCollectedJSRuntime::UnmarkSkippableJSHolders

Crash Reason EXCEPTION_ACCESS_VIOLATION_READ +++++++++++++++++++++++++++++++++++++++++++++++++++++ bp-7e1031a4-b270-4ff8-b46f-0c1f40220406 Signature: TraceCallbackFunc::Trace

Crash Reason EXCEPTION_ACCESS_VIOLATION_READ

This is for Sumo's Related Bugs 1204909 NEW --- crash in TraceCallbackFunc::Trace(JS::Heap<T>*, char const*, void*) in nsJSArgArray +++++++++++++++++++++++++++++++++++++++++++++++++++ bp-77a1aba2-a0ec-45b1-9f47-6263a0220406 Signature: js::GCMarker::markUntilBudgetExhausted

Crash Reason EXCEPTION_ACCESS_VIOLATION_READ

This is for Sumo's Related Bugs 719114 NEW --- Crash in [@ js::GCMarker::processMarkStackTop ] from heap corruption

more options

The crashes are all over the place. This might mean 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

https://support.mozilla.org/en-US/kb/firefox-uses-too-much-memory-or-cpu-resources


MemTest 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}