The crash reports are OOM (out of memory) reports where not enough contiguous free memory is available, so you may suffer from a memory leak that consumes all available memory.

You can create a new profile as a quick test to see if your current profile is causing the problem.

See "Creating a profile":

• https://support.mozilla.org/en-US/kb/profile-manager-create-remove-switch-firefox-profiles

If the new profile works, you can transfer files from a previously used profile to the new profile, but be cautious not to copy corrupted files to avoid carrying over problems.

• https://support.mozilla.org/en-US/kb/recovering-important-data-from-an-old-profile

It shouldn't crash on low memory if you have a bigger page file. Go into Windows Virtual Memory settings and make sure "Automatically manage paging files size for all drives" is enabled or the Windows volume is set to "System managed size".

It shouldn't crash on low memory if you have a bigger page file. Go into Windows Virtual Memory settings and make sure "Automatically manage paging files size for all drives" is enabled or the Windows volume is set to "System managed size".

Thanks, but I have a have a system managed page file, which is currently at 43Gb.

Are you sure it only happens when Firefox is running? Does memory usage recover when you close Firefox?

Take note of what websites are loaded before leaving Firefox idle for long periods, you can see a list by visiting about:processes. You can close processes from this list to avoid them potentially leaking memory over long periods.

Does it still happen when left in Troubleshoot Mode?