Pesquisar no site de suporte

Evite golpes de suporte. Nunca pedimos que você ligue ou envie uma mensagem de texto para um número de telefone, ou compartilhe informações pessoais. Denuncie atividades suspeitas usando a opção “Denunciar abuso”.

Saiba mais

Esta discussão foi arquivada. Faça uma nova pergunta se precisa de ajuda.

Fix For Memory Leak?

  • 3 respostas
  • 3 têm este problema
  • 5 visualizações
  • Última resposta de AHoff

more options

I am running Firefox 50.0.2 on a three month old computer with Windows 10 Home, 16 GB of memory and an Intel i7 3.4 GHz processor. Firefox routinely uses 2.5 GB or more of memory, and 15% or more of the CPU. I've tried the various fixes in the Mozilla support articles, and only one thing has worked to reduce memory and CPU usage: closing Firefox, deleting the content-prefs.sqlite file in my profile folder, and restarting Firefox. This immediately brings memory usage down to about 250-275 MB of memory and about 2% of the CPU. They stay near these levels for a while, but it doesn't take very long for both memory and CPU usage to rise to the higher levels, which makes Firefox slow and unresponsive. Not being a computer scientist or software engineer, I can't interpret this behavior, but possibly this will suggest a cause for the memory leak to some more knowledgeable person. I would be grateful for a solution - going through the shutdown/file deletion/restart procedure constantly is a pain.

I am running Firefox 50.0.2 on a three month old computer with Windows 10 Home, 16 GB of memory and an Intel i7 3.4 GHz processor. Firefox routinely uses 2.5 GB or more of memory, and 15% or more of the CPU. I've tried the various fixes in the Mozilla support articles, and only one thing has worked to reduce memory and CPU usage: closing Firefox, deleting the content-prefs.sqlite file in my profile folder, and restarting Firefox. This immediately brings memory usage down to about 250-275 MB of memory and about 2% of the CPU. They stay near these levels for a while, but it doesn't take very long for both memory and CPU usage to rise to the higher levels, which makes Firefox slow and unresponsive. Not being a computer scientist or software engineer, I can't interpret this behavior, but possibly this will suggest a cause for the memory leak to some more knowledgeable person. I would be grateful for a solution - going through the shutdown/file deletion/restart procedure constantly is a pain.

Todas as respostas (3)

more options

H AHoff, Sorry you are having problems.

Using more memory is not always a bad thing. You have 16GB of RAM, and may benefit from trying out the 64bit version of Firefox. That is new and not offered as standard for Windows users, but Linux & Mac users have had it for years.

See

See also

I would suggest you follow the steps in the article to Install 64 bit Firefox, but do NOT uninstall the 32bit version. Instead make sure you have a separate additional Firefox Profile for the new version.

Does the 64bit version work better ?

Using 15% of CPU should be no problem, and probably does not cause any slowdown.

On a 32 bit version of Firefox using 2.5GB could cause problems, however there could be other more important reasons for your problem and perceived slowness.

I am not too sure deleting content-prefs.sqlite would be expected to drastically change memory usage, maybe the effect is more from just closing and re-opening Firefox. Try closing then restarting Firefpox without deleting that settings file does that reduce the amount of memory apparently used ?

So we know what you are experiencing can you give some examples of what you mean by slow and unresponsive. explaining what you are trying to do and what you mean by slow - for example

  • Do you need to wait 5 or more seconds to key in each letter whilst typing word into replies ?
  • Does Video Freeze ?
  • Do websites take minutes to fully load ?

Have you tried similar tasks with both Edge & Internet Explorer, how do they compare to Firefox. (Firefox should be a similar speed, maybe sometimes even faster).

more options

Thanks for the quick reply. I haven't yet tried 64-bit Firefox, but I thought I would respond to your answer in the meantime. You are right that restarting Firefox, not deleting the content-prefs.sqlite file, is what brought memory and CPU usage down. Even without resorting to Task Manger, I can tell when memory and CPU usage has increased to high levels by Firefox becoming slow and unresponsive, by which I mean it is slow to respond to mouse and keyboard inputs: scrolling, typing, tab and text selection, clicking on links, etc. I often have to wait for the cursor to become active so I can click on a link. I've tried opening the same web page on both Firefox and Chrome, and didn't notice this behavior on Chrome, although I haven't given it a thorough test. I haven't noticed slow loading of websites or video freezes. Many thanks for your help - it's hard for a non-expert to understand why memory and CPU usage increase so much in the course of normal use.

more options

I've now tried 64 bit Firefox. Rather than installing a second version, I put the current portable 64 bit version (50.1.0) on my data partition and copied my profile to the portable version. This gave me two versions of the program that are identical except for the 32/64 bit difference. I'm not seeing a noticeable difference when running the 64 bit version. It is possible that it takes a little longer for the 64 bit version to run up memory and CPU usage, but that is very subjective and it wouldn't be a significant difference in any case. I can still tell when memory and CPU usage has gotten high by the slow response to keyboard and mouse inputs. For what it's worth, I am also running an almost identically configured 32 bit Firefox on my other desktop, which only has 8 GB of memory, and I am not experiencing this problem to nearly the same degree. I would greatly appreciate any additional advice, as this is a colossal nuisance. Also, as a matter of curiosity, I would be very interested in knowing what causes this enormous increase in resource usage. Thanks very much.