We're calling on all EU-based Mozillians with iOS or iPadOS devices to help us monitor Apple’s new browser choice screens. Join the effort to hold Big Tech to account!

Om de ûnderfining foar jo te ferbetterjen is tydlik de funksjonaliteit dan dizze website troch ûnderhâldswurk beheind. Wannear in artikel jo probleem net oplost en jo in fraach stelle wolle, kin ús stipemienskip jo helpe yn @FirefoxSupport op Twitter en /r/firefox op Reddit.

Sykje yn Support

Mij stipescams. Wy sille jo nea freegje in telefoannûmer te beljen, der in sms nei ta te stjoeren of persoanlike gegevens te dielen. Meld fertochte aktiviteit mei de opsje ‘Misbrûk melde’.

Mear ynfo

Dizze konversaasje is argivearre. Stel in nije fraach as jo help nedich hawwe.

recently Firefox tab crashes

  • 5 antwurd
  • 1 hat dit probleem
  • 1 werjefte
  • Lêste antwurd fan cor-el

more options

In the last 2 weeks or so, started having instances of tab crashing. Have refreshed Firefox. Problem occurs in troubleshoot mode. Have submitted crash reports.

In the last 2 weeks or so, started having instances of tab crashing. Have refreshed Firefox. Problem occurs in troubleshoot mode. Have submitted crash reports.

Alle antwurden (5)

more options

In the address bar, type about:crashes<enter>. Note: If any reports do not have BP- in front of the numbers/letters, click it to submit them.

The crash report is several pages of data. We need the report numbers to see the whole report.

Using your mouse, mark the most recent 7 - 10 Submitted crash reports, and copy them. Now go to the reply box and paste them in.

Please, Do not post a screenshot ! !

aboutcrashesFx57

For more help on crash reports, see; https://support.mozilla.org/en-US/kb/firefox-crashes-asking-support

more options

bp-30b0295c-bf70-4af0-bd62-20a3b0210626 6/26/2021, 12:53 PM View bp-24a659f9-10ba-4292-8ccb-123cd0210626 6/26/2021, 12:53 PM View bp-79a9ccb0-4a96-40dd-8c3b-5dace0210626 6/26/2021, 12:53 PM View bp-a804ecb7-c2df-4206-b719-37b490210626 6/26/2021, 12:53 PM View

more options

The crash reports are OOM (out of memory) reports where not enough contiguous free memory is available.

  • MOZ_CRASH Reason (Sanitized) : [unhandlable oom] Failed not allocate new chunk during GC
Available Page File : 597,700,608 bytes (597.7 MB)
Available Physical Memory : 6,699,831,296 bytes (6.7 GB)
System Memory Use Percentage : 60
OOM Allocation Size : 1,048,576 bytes (1.05 MB)

Do you let Windows handle the Page file automatically or have you set a fixed size for the Windows Page File ?

  • Control Panel -> System -> Advanced -> Performance -> Settings

If you use a fixed size for the page file then try the automatic setting and let Windows handle the page file automatically.

more options

Changed the page file size to be managed automatically. That's all well and good, but I wonder why the problem recently started happening.

more options

Maybe you are running other software that uses a lot of memory. You can possibly check this in the Windows Task Manager (Ctrl+Shift+ESC).