Product Firefox Release Channel release Version 95.0.2 Build ID 20211218203254 (2021-12-18)

bp-a2292ef9-ca66-4781-9d4d-8b26d0211222 bp-3c425efa-43d0-4dad-b699-6689b0211220

Signature: OOM | large | mozalloc_abort | xul.dll | _PR_NativeRunThread | pr_root

MOZ_CRASH Reason (Sanitized) : out of memory: 0x0000000000100000 bytes requested

Crash Reason EXCEPTION_BREAKPOINT

xul.dll = Firefox

This is for Sumo's Related Bugs 1725571 NEW --- Windows 7 x86 Crash in [@ OOM | large | mozalloc_abort | xul.dll | _PR_NativeRunThread | pr_root]

1658415 RESOLVED FIXED Neqo Socket Thread Crash in [@ OOM | large | mozalloc_abort | xul.dll | _PR_NativeRunThread | pr_root] +++++++++++++++++++++++++++++++++++++++++++++++++++++++ Product Firefox Release Channel release Version 95.0.1 Build ID 20211215221728 (2021-12-15)

bp-7a3054f3-7513-4a2e-920e-5839b0211222 Signature: OOM | large | mozalloc_abort | xul.dll | _PR_NativeRunThread | pr_root

Uptime 12 seconds

MOZ_CRASH Reason (Sanitized) : out of memory: 0x0000000000100000 bytes requested

Crash Reason EXCEPTION_BREAKPOINT

xul.dll = Firefox

This is for Sumo's Related Bugs 1725571 NEW --- Windows 7 x86 Crash in [@ OOM | large | mozalloc_abort | xul.dll | _PR_NativeRunThread | pr_root]

1658415 RESOLVED FIXED Neqo Socket Thread Crash in [@ OOM | large | mozalloc_abort | xul.dll | _PR_NativeRunThread | pr_root]

Basically, an OOM (Out Of Memory) means 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}

I ran Memtest86+ 5.31b: - default configuration: 7 pass, 0 errors - F12 configuration: 1 pass, 0 error

I did change the page file managing in order to let Windows handle it

Everything is Ok until now.

Thank you so much.

Best wishes on Christmas,

Fraulf

Glad to help. Safe Surfing.

Hi FredMcD,

I had crashing again on December 24th (see images attached) and others until today:

bp-e9e5b8eb-f655-43a8-bc16-562a80211228 bp-34a0954a-5e68-4778-90e3-fecce0211228 bp-219bc3bc-f40c-401e-a403-b9d140211228 bp-56cf2ed0-bfb1-4bef-b0a0-52fdb0211222

Some help, again, will be appreciated.

Regards,

Fraulf

I can't read the messages in the pictures you posted. What do they say?

Product Firefox Release Channel release Version 95.0.2 Build ID 20211218203254 (2021-12-18)

bp-e9e5b8eb-f655-43a8-bc16-562a80211228 Signature: OOM | large | mozalloc_abort | xul.dll | _PR_NativeRunThread | pr_root

MOZ_CRASH Reason (Sanitized) : out of memory: 0x0000000000100000 bytes requested

Crash Reason EXCEPTION_BREAKPOINT

System Memory Use Percentage 93

This is for Sumo's Related Bugs 1725571 NEW --- Windows 7 x86 Crash in [@ OOM | large | mozalloc_abort | xul.dll | _PR_NativeRunThread | pr_root]

1658415 RESOLVED FIXED Neqo Socket Thread Crash in [@ OOM | large | mozalloc_abort | xul.dll | _PR_NativeRunThread | pr_root] ++++++++++++++++++++++++++++++++++++++++++++++++ bp-34a0954a-5e68-4778-90e3-fecce0211228 Signature: OOM | large | xul.dll | _PR_NativeRunThread | pr_root

MOZ_CRASH Reason (Sanitized) : MOZ_CRASH(OOM)

Crash Reason EXCEPTION_BREAKPOINT

This is for Sumo's Related Bugs 1725571 NEW --- Windows 7 x86 Crash in [@ OOM | large | mozalloc_abort | xul.dll | _PR_NativeRunThread | pr_root] +++++++++++++++++++++++++++++++++++++++++++++++++ bp-219bc3bc-f40c-401e-a403-b9d140211228 Signature: _CreateWindowEx

Crash Reason EXCEPTION_ACCESS_VIOLATION_EXEC

This is for Sumo's Related Bugs 1730033 RESOLVED FIXED Crash in [@ _CreateWindowEx] from mscom::ProcessRuntime::ProcessRuntime

A post was flagged as Solved Problem. If the problem is not solved, please remove that flag. If you don’t, others that can help may not read this post.

Go to that message, and use the Undo link to its right.

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.

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

You may not need the latter (32-bit version) if you use 64-bit Firefox. You may have to reboot the computer. ++++++++++++++++++++++++++++++++++++++++++++++ In another thread, a user reported that a recent update of Malwarebytes Anti-Exploit (version 415) may be causing symptoms similar to the VC Runtime problem. If you have MBAE, it should have a setting to exempt Firefox. You could test whether that makes any difference.