Hi Andres, sorry to hear about this problem. That crash report has the signature "[@ OOM | small ]" indicating that Firefox requested a block of contiguous memory from the system and the system rejected the request.

The report shows memory use was 90%, which is a high-ish, but not at a critical stage. I think the real problem must be that memory became very fragmented so no blocks of the requested size were available. Unfortunately, I don't know of a way to manage these kinds of crashes in advance -- the system should take care of memory allocation automatically. ??

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 ? If you use a fixed size for the page file then try the former and let Windows handle the page file.