Join the AMA (Ask Me Anything) with the Firefox leadership team to celebrate Firefox 20th anniversary and discuss Firefox’s future on Mozilla Connect. Mark your calendar on Thursday, November 14, 18:00 - 20:00 UTC!

This site will have limited functionality while we undergo maintenance to improve your experience. If an article doesn't solve your issue and you want to ask a question, we have our support community waiting to help you at @FirefoxSupport on Twitter and/r/firefox on Reddit.

Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Natao arisiva ity resaka mitohy ity. Mametraha fanontaniana azafady raha mila fanampiana.

Choppy Firefox Browsing

  • 2 valiny
  • 1 manana an'ity olana ity
  • 1 view
  • Valiny farany nomen'i 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."

All Replies (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?

Novain'i Renard d'Allan t@

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.