Avatar for Username

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

Lolu chungechunge lwabekwa kunqolobane. Uyacelwa ubuze umbuzo omusha uma udinga usizo.

When will you get rid of the resource hog, "Plugin-Container.exe"

  • 3 uphendule
  • 300 zinale nkinga
  • 4 views
  • Igcine ukuphendulwa ngu joesao

AnonymousUser
AnonymousUser
more options

Plugin-container-exe has a memory leak. When you go in and out of numerous web sites, it consumes more and more and more memory and turns my computer into a dog. Since the inclusion of the plugin-container, explorer is now a better browser.

This happened

Every time Firefox opened

== The last update that included plugin-container.

Plugin-container-exe has a memory leak. When you go in and out of numerous web sites, it consumes more and more and more memory and turns my computer into a dog. Since the inclusion of the plugin-container, explorer is now a better browser. == This happened == Every time Firefox opened == The last update that included plugin-container.

All Replies (3)

Shawn
Shawn
  • Moderator
more options

If you want to disable plugin-container, See this KB article: http://kb.mozillazine.org/Plugin-container_and_out-of-process_plugins

AnonymousUser
AnonymousUser Umnikazi wombuzo
more options

Sounds like it is time to move to Chrome. In the last several months Firefox has slowed to less than a crawl.

Is this a lesson on how to lose 70% market share and tube your business. Sounds like Abobe, Apple and Microsoft got together and designed the perfect bomb for Firefox wrapped in the form of a flash drive.

joesao
joesao
more options

Are you serious that this is your "solution"? I did as you suggested -- changed the flags to "false" -- and now I restared Firefox with a mere 10 tabs open (no videos; just a few text pages, gmail, yahoo finance, barrons.com) and Firefox is consuming 1.1 gb of RAM. What's the reason behind this? It looks like whatever resources were being swallowed by plugin-container.exe are now being swallowed by Firefox itself, so that doesn't solve the problem.

Is Firefox a good idea taken too far? When it began, the Firefox project was a fast, nimble browser. Is it now too bloated and convoluted to be of any use? Is it a victim of its success?