Where did you install Firefox from? Help Mozilla uncover 3rd party websites that offer problematic Firefox installation by taking part in our campaign. There will be swag, and you'll be featured in our blog if you manage to report at least 10 valid reports!

Avatar for Username

Sök i support

Akta dig för supportbedrägerier: Vi kommer aldrig att be dig att ringa eller skicka ett sms till ett telefonnummer eller dela personlig information. Rapportera misstänkt aktivitet med alternativet "Rapportera missbruk".

Learn More

Denna tråd har arkiverats. Ställ en ny fråga om du behöver hjälp.

Why do the Firefox and Plugin-Container processes take up so much memory?

  • 2 svar
  • 19 har detta problem
  • 2 visningar
  • Senaste svar av NickR25

NickR25
NickR25
more options

I don't think I really need to go into much detail other than provide this screen capture: http://i55.tinypic.com/ctfvb.png

There's no way this is normal; What could be the cause of the issue and how do I go about resolving it?

I don't think I really need to go into much detail other than provide this screen capture: http://i55.tinypic.com/ctfvb.png There's no way this is normal; What could be the cause of the issue and how do I go about resolving it?

Alla svar (2)

pramaganus
pramaganus
more options

As far as i know plugin container.exe holds your loaded plug-ins, if u terminate it while for example watching a youtube clip, youll get a message that flash player has crashed. So disable some plugins. I have quite the same problem, http://i55.tinypic.com/29bdqg9.png but the firefox.exe is the one eating my ram, iv disabled everything i dont use, left just a few addons (add block+, download status bar, flagfox, open in new tab & search preview with tin eye addon) In extensions i have java, media player, shokwawe plugins active. I rly turned off all i could, but still FF takes tons of RAM :/

NickR25
NickR25 Frågans ägare
more options

This is a serious issue and really is making Chrome look a great deal more appealing right now. Firefox is the greatest, indeed, but I've never had so many issues with a mere web browser; this has happened in previous versions, too, so I guess functionality isn't a priority.