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

Why is Firefox so damn slow with 16G DDR3 memory on a Sandy Bridge CPU?

  • 3 replies
  • 5 have this problem
  • 87 views
  • Last reply by John99

more options

As I am writing this message on this forum I have 63 open tabs in Firefox version 10.0. None of them are streaming video or anything like that. They are static pages.

I am running Windows 7 64-bit Ultimate on a Sandybridge Core i3-2105 CPU. I have 16GB of DDR3 1600 memory. Why does a simplistic browser run slower than a 3d video game? I am using the integrated graphics on the Sandybridge CPU(Intel HD3000 graphics). But I don't think the graphics are what causes the slow performance. I don't understand why I can't have a 100+ tabs open in Firefox and get instantaneous tab switching with a system as powerful as I have. Tell me what I must do to make this slowness go away, please, somebody. Thank You.

All Replies (3)

more options

I would not expect Firefox to be slow on such a system. I am not having problems and have much less powerful systems than yours. I would expect it will turn out to be related to the Firefox extensions that you are using so try in Diagnose Firefox issues using Troubleshoot Mode.

Developers are looking into speeding up Firefox, but simply switching between tabs should not be a problem.

(As background info you may be interested in

more options

I have taken your advice and from what I can tell so far it does appear to be much more responsive. Thank you for your help.

more options

Glad to hear it has improved.

One of the biggest advantages of Firefox is that is is almost infinitely customisable.
One of the biggest disadvantages of Firefox is that is is almost infinitely customisable.

When it comes to troubleshooting any problems, the software extensions may introduce memory leaks or unexpected interactions and so it is best to start again in the basic safe mode. It simplifies the situation and allows comparisons and tests to run under known and comparable circumstances, that is an inconvenient necessity. I hope you manage to narrow down the problem and ultimately find what is causing it.