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.

Firefox crashes

more options

My Firefox has been crashing numerous times per day and I have not been able to root out the cause. Most recent: Crash ID: bp-509b285a-7d76-40f1-af25-78d371171106

My Firefox has been crashing numerous times per day and I have not been able to root out the cause. Most recent: Crash ID: bp-509b285a-7d76-40f1-af25-78d371171106

Alle antwurden (2)

more options

Please consider turning on send info to Mozilla before posting a question. This helps us help you. As I have no info from your system that would help see things that cause this issue/s.

The crash report is a shutdown hang where Firefox takes too long to close. This is often related to outdated and or corrupted video card drivers and Flash.

https://support.mozilla.org/en-US/kb/upgrade-graphics-drivers-use-hardware-acceleration TRY NO ACCELERATION and https://support.mozilla.org/en-US/kb/troubleshoot-extensions-themes-to-fix-problems?redirectlocale=en-US&redirectslug=Troubleshooting+extensions+and+themes

Please let us know if this solved your issue or if need further assistance.

more options

Do you have any other recent crash reports that might help show a pattern?

This one indicates Firefox was in its Safe Mode -- all extensions disabled, hardware acceleration disabled, JavaScript compilers disabled -- so that rules out a lot of possibilities.

The report does indicate memory was 80% full, and possibly some of the pre-crash functions were seeking to access more memory, but the report does not say Firefox crashed due to running out of memory. I'm not sure what to make of it (I'm not a software engineer!).