Firefox has crashed intermittently since update to 92.0.2

Your current version is 90.0.2

Product Firefox Release Channel release Version 90.0.2 Build ID 20210721174149 (2021-07-21) Buildhub data OS Windows 10 OS Version 10.0.19043

Tue, 27 Jul 2021 20:32:04 GMT bp-4fb2010a-ff3c-4046-80ce-3ba000210804 Signature: js::gc::TraceEdgeInternal<T>

Uptime 0 seconds

Crash Reason EXCEPTION_ACCESS_VIOLATION_READ

SafeMode : 0

StartupCrash : 0

This is for Sumo's Related Bugs You are not authorized to access bug 1474623. +++++++++++++++++++++++++++++++++++++++++++++++++++ Tue, 27 Jul 2021 20:34:15 GMT bp-c55f0c55-730e-4767-9cbd-b6def0210804 Signature: js::Scope::finalize

Uptime 44 seconds

Crash Reason EXCEPTION_ACCESS_VIOLATION_READ +++++++++++++++++++++++++++++++++++++++++++++++++ Tue, 27 Jul 2021 20:46:47 GMT bp-ec4f4c9b-2b58-4450-9b41-af5a70210804 Signature: mozilla::CycleCollectedJSRuntime::JSObjectsTenured

Crash Reason EXCEPTION_ACCESS_VIOLATION_READ

This is for Sumo's Related Bugs 1584796 NEW --- Crash in [@ mozilla::CycleCollectedJSRuntime::JSObjectsTenured] +++++++++++++++++++++++++++++++++++++++++++++++ Tue, 27 Jul 2021 21:36:57 GMT bp-391d7abf-68dc-497c-9762-6cfed0210804 Signature: js::TenuringTracer::onObjectEdge

Uptime 228 seconds (3 minutes and 48 seconds)

Crash Reason EXCEPTION_ACCESS_VIOLATION_READ

This is for Sumo's Related Bugs 1582214 NEW --- Crash in [@ js::TenuringTracer::traverse<T>] +++++++++++++++++++++++++++++++++++++++++++++ Wed, 28 Jul 2021 00:13:29 GMT bp-4fff08a3-aaa0-45e6-81d2-2befa0210804 Signature: mozilla::CycleCollectedJSRuntime::TraceNativeGrayRoots

Uptime 8,929 seconds (2 hours, 28 minutes and 49 seconds)

Crash Reason EXCEPTION_ACCESS_VIOLATION_READ

We have seen a log of problems on this of late.

You can check for issues caused by a corrupted or incomplete Visual C++ installation that is missing runtime components (Redistributable Packages) required by Firefox, especially VCRUNTIME140_1.dll.

I would install both 32-bit and 64-bit "Visual Studio 2015, 2017 and 2019" downloads, (x86: vc_redist.x86.exe and x64: vc_redist.x64.exe) from https://support.microsoft.com/help/2977003/the-latest-supported-visual-c-downloads

Note that the crash reports you posted happened about a week ago. Do you have more recent reports or are they throttled and can't be submitted ?

If there aren't recent reports then this might not be a crash, but something else. You can also check the Windows Event logs to see whether this issue shows up in this log.

FredMcD:

My apologies version error I am somewhat dyslexic with numbers. Now that you pointed it out I can see the error.

I applied both Visual Studio updates. Will advise if this fixes it.

cor-el:

I thought I sent the latest ones in About:crashes, I am not sure why these are from a week ago and not the one from 08/03/21. These are the rest dated yesterday when I submitted them: bp-4fff08a3-aaa0-45e6-81d2-2befa0210804 8/3/2021, 9:43 PM View bp-d4003211-45b3-495f-8d30-9b58b0210804 8/3/2021, 9:43 PM View bp-fd852508-3165-4dff-9bc6-55ce40210804 8/3/2021, 9:43 PM View bp-d8755c5f-9b7e-4284-bbd9-34bad0210804 8/3/2021, 9:43 PM View bp-3079d240-5811-4f55-8030-d6ee40210804 8/3/2021, 9:43 PM View bp-ae581b27-d19c-4e43-bd1c-42e4f0210804 8/3/2021, 9:43 PM View

bp-d4003211-45b3-495f-8d30-9b58b0210804 Signature: js::jit::MaybeEnterJit

Crash Reason EXCEPTION_ACCESS_VIOLATION_EXEC

This is for Sumo's Related Bugs 1665579 RESOLVED DUPLICATE Crash in [@ js::jit::MaybeEnterJit] with javascript.options.warp enabled

1665432 VERIFIED FIXED Crash [@ ??] with new.target

1461724 NEW --- [ARM/ARM64] Crash in js::jit::MaybeEnterJit (SIGILL/SIGSEG on Xperia X/Xperia Z5/Galaxy S6/Galaxy S2 Tab)

1461480 RESOLVED INCOMPLETE [ARM64] Crash in js::jit::MaybeEnterJit (1MB aligned address)

1451720 NEW --- MaybeEnterJIT SIGSEGV crashes on Android/ARM64 (occasional)

1425132 RESOLVED DUPLICATE Crash in js::jit::MaybeEnterJit

858032 NEW --- [meta] crashes in EnterBaseline / EnterJit +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ bp-fd852508-3165-4dff-9bc6-55ce40210804 Signature: js::gc::TraceEdgeInternal<T>

Crash Reason EXCEPTION_ACCESS_VIOLATION_READ

This is for Sumo's Related Bugs 1474623 You are not authorized to access bug 1474623 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ bp-d8755c5f-9b7e-4284-bbd9-34bad0210804 Signature: mozilla::FrameLayerBuilder::RemoveFrameFromLayerManager

Crash Reason EXCEPTION_ACCESS_VIOLATION_READ

This is for Sumo's Related Bugs 1469505 RESOLVED DUPLICATE Crash in mozilla::FrameLayerBuilder::RemoveFrameFromLayerManager +++++++++++++++++++++++++++++++++++++++++++++++++++++++++ bp-3079d240-5811-4f55-8030-d6ee40210804 Signature: nsCOMArray_base::~nsCOMArray_base

Crash Reason EXCEPTION_ACCESS_VIOLATION_READ

The crash reports are all over the place. Sometimes this means a problem 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}

FredMcD:

I am running a system managed page file.

You were right after running Memtest86 (your link in email was blocked by Bitdefender) I found errors so I ran it for each 8GB DIMM individually and one of my 8GB DIMM is bad. I running on 8GB for now with the good one until I can get it replaced.

Hopefully that will fix it.

Thanks, D

Let's hope that was the only problem.

If that fixes the problem, please flag your last post as Solved Problem as this can help others with similar problems.