Important Notice: We're experiencing email notification issues. If you've posted a question in the community forums recently, please check your profile manually for responses while we're working to fix this.

On Monday the 3rd of March, around 5pm UTC (9am PT) users may experience a brief period of downtime while one of our underlying services is under maintenance.

Mozilla 도움말 검색

고객 지원 사기를 피하세요. 저희는 여러분께 절대로 전화를 걸거나 문자를 보내거나 개인 정보를 공유하도록 요청하지 않습니다. "악용 사례 신고"옵션을 사용하여 의심스러운 활동을 신고해 주세요.

자세히 살펴보기

Why is Firefox slow after latest update?

  • 9 답장
  • 154 이 문제를 만남
  • 1 보기
  • 최종 답변자: Kiwi8

more options

I just updated to v24 and it is really lagging a lot. I've tried resetting, disabling add ons, updating add ons, restarting in safe mode... the whole nine yards. I've done every troubleshooting I can think of and it is still really laggy and slow. I have Windows 7 and a 64bit system. I didn't have this problem until the latest update.

I just updated to v24 and it is really lagging a lot. I've tried resetting, disabling add ons, updating add ons, restarting in safe mode... the whole nine yards. I've done every troubleshooting I can think of and it is still really laggy and slow. I have Windows 7 and a 64bit system. I didn't have this problem until the latest update.

모든 댓글 (9)

more options
more options

Maybe it is possible caudes by duplicated files after the updating. You can go to local disk to delete juck files. Also you can clear out all cookies and browsing history out from your Main Internet Browser to upgrade Online Experience

more options

Usually slowness after one upgrade requires disabling hardware acceleration, or a possible new regression (hopefully not).

You might need to restart Firefox in order for this to take effect, so save all work first (e.g., mail you are composing, online documents you're editing, etc.).

Then perform these steps:

  • Click the orange Firefox button at the top left, then select the "Options" button, or, if there is no Firefox button at the top, go to Tools > Options.
  • In the Firefox options window click the Advanced tab, then select "General".
  • In the settings list, you should find the Use hardware acceleration when available checkbox. Uncheck this checkbox.
  • Now, restart Firefox and see if the problems persist.

Additionally, please check for updates for your graphics driver by following the steps mentioned in the following Knowledge base articles:

more options

Thanks, it appears to be working a bit better now. I'm not sure what fixed it, though, but thanks for the responses.

more options

hardware acceleration was already unchecked on mine - it does this after every single update, even in safemode with everything disabled.

more options

This always seems to happen with updates. They fix a bunch of bugs, but create new ones, or don't fix old persisting ones. I was under the impression that Firefox speeds up with every update, but it would seem to be the opposite. I am perturbed that users have to jump through hoops to find workarounds. eg. Things were working just fine before, now that it isn't after the new update, we have to delete old user profiles, dig through subfolders to find duplicate files created to delete, and restart from scratch. Which can take hours of your time. All because Firefox messed things up. If Firefox broke it, they should fix it. Not us, we don't get paid to do their job. I'm always for "if it's not broke, don't break it, so you don't have to fix it." Also what's the point of having a "hardware acceleration" feature, if it doesn't work?

글쓴이 gslrider 수정일시

more options

Still the same with v25.

more options

v25 is actually working much better for me now. I still notice after a while of Firefox being open and used, it does still tend to slow down. But much less than v24. ie. scrolling stutters, but no longer hangs for a few seconds. Deleting history, and cache doesn't help. But restarting Firefox does. Until it starts happening again. Better than nothing. Better than using Chrome. And definitely better than the previous version.

more options

Version 26 seems to have solved this problem.