Cerca nel supporto

Attenzione alle mail truffa. Mozilla non chiederà mai di chiamare o mandare messaggi a un numero di telefono o di inviare dati personali. Segnalare qualsiasi attività sospetta utilizzando l'opzione “Segnala abuso”.

Ulteriori informazioni

Questa discussione è archiviata. Inserire una nuova richiesta se occorre aiuto.

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

  • 3 risposte
  • 300 hanno questo problema
  • 4 visualizzazioni
  • Ultima risposta di joesao

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.

Tutte le risposte (3)

more options

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

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.

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?