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

ค้นหาฝ่ายสนับสนุน

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.

เรียนรู้เพิ่มเติม

หัวข้อนี้ถูกเก็บถาวรแล้ว โปรดถามคำถามใหม่หากคุณต้องการความช่วยเหลือ

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

  • 2 การตอบกลับ
  • 19 คนมีปัญหานี้
  • 2 ครั้งที่ดู
  • ตอบกลับล่าสุดโดย 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?

การตอบกลับทั้งหมด (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 เจ้าของคำถาม
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.