bp-11c94bfb-246a-4d3d-8ce1-4c8c61171008 Signature: OOM | large | js::AutoEnterOOMUnsafeRegion::crash | js::AutoEnterOOMUnsafeRegion::crash | js::TenuringTracer::moveToTenured

mbae.dll = Malwarebytes Anti-Exploit

ipseng32.dll = Symantec Intrusion Detection = Symantec Corporation

nvd3dum.dll = NVIDIA Windows Vista WDDM driver

This is for Sumo's Related Bugs 1365207 RESOLVED DUPLICATE Crash in OOM | large | js::AutoEnterOOMUnsafeRegion::crash | js::AutoEnterOOMUnsafeRegion::crash | js::TenuringTracer::moveToTenured

1337105 NEW --- Crash in OOM | large | js::AutoEnterOOMUnsafeRegion::crash | js::AutoEnterOOMUnsafeRegion::crash | js::TenuringTracer::moveToTenured [related to Microsoft's Enhanced Mitigation Experience Toolkit (EMET)]

1257387 NEW --- crash in OOM | unknown | js::AutoEnterOOMUnsafeRegion::crash | js::TenuringTracer::moveToTenured

Update Malwarebytes. If the problem continues, disable it.

Thank you for the crash reports. Three of them show that system memory use was 80% or higher, which can lead to Firefox not getting memory it wants from Windows and halting a a result. (Maybe Firefox should just back off from the specific thing it is trying to do in that situation? I don't know if that is possible... just a thought.)

The two older reports were requests for a relatively modest amount of memory, but the two newer ones were requests for a megabyte of memory, which surprises me. What could require such a large amount of memory all at once? Maybe some large media?

Can you associate these crashes with any particular sites or kinds of web content?

FredMcD said

bp-11c94bfb-246a-4d3d-8ce1-4c8c61171008 Signature: OOM | large | js::AutoEnterOOMUnsafeRegion::crash | js::AutoEnterOOMUnsafeRegion::crash | js::TenuringTracer::moveToTenured mbae.dll = Malwarebytes Anti-Exploit ipseng32.dll = Symantec Intrusion Detection = Symantec Corporation nvd3dum.dll = NVIDIA Windows Vista WDDM driver This is for Sumo's Related Bugs 1365207 RESOLVED DUPLICATE Crash in OOM | large | js::AutoEnterOOMUnsafeRegion::crash | js::AutoEnterOOMUnsafeRegion::crash | js::TenuringTracer::moveToTenured 1337105 NEW --- Crash in OOM | large | js::AutoEnterOOMUnsafeRegion::crash | js::AutoEnterOOMUnsafeRegion::crash | js::TenuringTracer::moveToTenured [related to Microsoft's Enhanced Mitigation Experience Toolkit (EMET)] 1257387 NEW --- crash in OOM | unknown | js::AutoEnterOOMUnsafeRegion::crash | js::TenuringTracer::moveToTenured

Thank you for the reply. However, it is written in the same cryptic language as the crash report itself, which I cannot get anything out of it.

FredMcD said

Update Malwarebytes. If the problem continues, disable it.

I have had Malwarebytes for years and Firefox worked fine with it in the past. It is the premium version and it updates itself periodically to stay up-to-date all the time. I cannot disable it since it provides good protection. If this is the only option I have, then I will adopt another browser.

jscher2000 said

Thank you for the crash reports. Three of them show that system memory use was 80% or higher, which can lead to Firefox not getting memory it wants from Windows and halting a a result. (Maybe Firefox should just back off from the specific thing it is trying to do in that situation? I don't know if that is possible... just a thought.) The two older reports were requests for a relatively modest amount of memory, but the two newer ones were requests for a megabyte of memory, which surprises me. What could require such a large amount of memory all at once? Maybe some large media? Can you associate these crashes with any particular sites or kinds of web content?

Thank you for replying to my post. It seems that it happens more frequently when CNN web site is launched. I am trying now to avoid launching this web site and see what happens.

Hi, try disabling to test, Symantec/Norton Intrusion Detection. You could also try holding down Shift when you start Firefox to start in Safe Mode. More - Diagnose Firefox issues using Troubleshoot Mode