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.

Choppy Firefox Browsing

  • 2 antwurd
  • 1 hat dit probleem
  • 1 werjefte
  • Lêste antwurd fan cdb13

more options

For the last 2 days, Firefox has been constantly in a "processing" mode, stopping/starting. I have started in the safe mode and I have reset Firefox to no avail. While the revolving circle (processing symbol?) is active, there is a message at the top of my screen indicating that Firefox is "not responding."

For the last 2 days, Firefox has been constantly in a "processing" mode, stopping/starting. I have started in the safe mode and I have reset Firefox to no avail. While the revolving circle (processing symbol?) is active, there is a message at the top of my screen indicating that Firefox is "not responding."

Alle antwurden (2)

more options

What are your PC's specs? You know, who made it, how old it is, how much RAM is has, blah blah blah....

Also, how long has this problem existed? Did something happen that might have triggered it?

Bewurke troch Renard d'Allan op

more options

The computer is an HP, and about 4 years old. Intel i3 chip, running Windows 7 Home. I have not had any problems with the system, nor have I made any modifications. I was away from the office for about 10 days, with the computer shut down. Firefox has been like this since I rebooted. Thanks for looking into this issue.