Eheka Pytyvõha

Emboyke pytyvõha apovai. Ndorojeruremo’ãi ehenói térã eñe’ẽmondóvo pumbyrýpe ha emoherakuãvo marandu nemba’etéva. Emombe’u tembiapo imarãkuaáva ko “Marandu iñañáva” rupive.

Learn More

Firefox crashes repeatedly even in Troubleshoot mode

  • 4 Mbohovái
  • 0 oguereko ko apañuãi
  • 2 Hecha
  • Mbohovái ipaháva adalgisa_b

more options

Hi, this is an ongoing problem, but I just submitted my first crash report. I can open the browser, but it crashes- it seems randomly, after I've had it open a while. I generally have 4 or 5 tabs open, not a ton. Running Windows 10 Pro version 21H2. Not sure why I'm including crash id in a community support group, but you said to do so...

b1c0c1af-7c94-448f-97dd-d40b79ff4731

Hi, this is an ongoing problem, but I just submitted my first crash report. I can open the browser, but it crashes- it seems randomly, after I've had it open a while. I generally have 4 or 5 tabs open, not a ton. Running Windows 10 Pro version 21H2. Not sure why I'm including crash id in a community support group, but you said to do so... b1c0c1af-7c94-448f-97dd-d40b79ff4731

Opaite Mbohovái (4)

more options

Hi, thank you for the ID. Normally after a successful submission the code changes to a different one that starts with bp. Alternately, you can click the link to the report up on the crash-stats server and then share the URL from there in a reply here (here at https://support.mozilla.org/questions/1391742, not by email).

¿Imba’eporãva?

more options

Thanks for the response- do you mean this report? bp-99699478-680f-4e29-b1f2-32cc70221005 https://crash-stats.mozilla.org/report/index/99699478-680f-4e29-b1f2-32cc70221005

¿Imba’eporãva?

more options

Yes, thanks.

That one is an "OOM" or "out of memory" error. It says Firefox asked the system for an allocation of 131,072 bytes (131.07 KB; "OOM Allocation Size" row). Since it wasn't available, Firefox crashed.

This probably indicates memory fragmentation more than memory actually being completely full. What's strange is that Firefox crashing and restarting didn't resolve the issue (I assumed Windows would take the opportunity to reorganize memory when a program closes, but maybe not).

One thing that jumps out at me in the report is

Available Page File 28,172,288 bytes (28.17 MB)

Usually the page file is several gigabytes and doesn't get this congested, so this could indicate a nearly full hard drive, or the page file being on a smaller partition, or perhaps a setting restricting the page file size, any of which might prevent smooth use of virtual memory when programs needs more memory. Does something need to be done here? Unfortunately, that is out of my area of expertise.

In Firefox itself, maybe some memory tips would help? Firefox uses too much memory or CPU resources - How to fix

¿Imba’eporãva?

more options

Thank you, I'll look into this. The pagefile is on the same partition, and is set to 12.288 gigabytes. Hard drive is about 80% full. I don't usually have more than a couple of apps open... Thanks for the link, I'll check it out.

¿Imba’eporãva?

Eporandumína

Nde eikéke nde mba’etepe embohovái hag̃ua ñe’ẽmondo. Ikatúpa, emoñepyrũ peteĩ porandu, ndereguerekói gueteriramo nemba’ete.