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.

Avatar for Username

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

Echekwara usoro a. Biko jụọ ajụjụ ọhụrụ ma ọ bụrụ na ị chọrọ enyemaka.

slow on OSX, frequent short glimpses on beachball even if just scrolling

elcaro
elcaro
more options

FF seems very unresponsive - for example when I clicked in this box to type this I got a brief beachball! FF can be showing up to 50% of my CPU use - whoops just got another look at the beachball - when I'm using some other application and not even in FF. I sometimes have 2 or 3 windows open but w/o any animation afaik.

FF seems very unresponsive - for example when I clicked in this box to type this I got a brief beachball! FF can be showing up to 50% of my CPU use - whoops just got another look at the beachball - when I'm using some other application and not even in FF. I sometimes have 2 or 3 windows open but w/o any animation afaik.

All Replies (2)

dannz
dannz
more options

I've been having this problem - but just did check to validate fonts in Fontbook. No bad fonts as such, but several fonts were flagged 'minor problem proceed with caution'. After removing these, font cache cleaned, running 'all maintenance tasks' in Ice Clean and system rebooted this problems seems to have been resolved. (for me at least).

If anyone else having this issue finds resolving font management issues does or doesn't fix this, please post so can help pin down cause of this problem.

rbarline
rbarline
more options

Open Activity Monitor (AM) and watch CPU activity. Sort processes list by % CPU utilization. FF should come to the top. Open a web site that gives you a long page. Resize FF window so you can see AM at the same time and watch FF % while you scroll rapidly up and down the page. You can see that this sometimes pegs the CPU to 100%. When that happens you'll get a spinning beachball. The question is - why does it take so much CPU cycles to scroll a window in FF? I'm on version 3.6.17 and get the beachball almost every time I scroll. Do the same experiment with Safari and note the difference - Safari % hardly changes at all no matter how fast you scroll. Go figure.

Edeziri site na rbarline