Important Notice: We're experiencing email notification issues. If you've posted a question in the community forums recently, please check your profile manually for responses while we're working to fix this.

Avatar for Username

Hilfe durchsuchen

Vorsicht vor Support-Betrug: Wir fordern Sie niemals auf, eine Telefonnummer anzurufen, eine SMS an eine Telefonnummer zu senden oder persönliche Daten preiszugeben. Bitte melden Sie verdächtige Aktivitäten über die Funktion „Missbrauch melden“.

Weitere Informationen

Dieses Thema wurde archiviert. Bitte stellen Sie eine neue Frage, wenn Sie Hilfe benötigen.

Plugin conatainer still eating ram without any plugins

  • 6 Antworten
  • 34 haben dieses Problem
  • 4 Aufrufe
  • Letzte Antwort von philipp

ownageismagic
ownageismagic
more options

All plugins set to Never Activate, no addons installed, default theme. Plugin container still starting and constantly eating ram. Now it consumes 940 mb and keep going up. If I kill this process all open tabs crashes and afeter 30 sec plugin container restarting and continue rising mem usage from 100mb. Also it reads and writes disk at around 0.1Mb/s rate

All plugins set to Never Activate, no addons installed, default theme. Plugin container still starting and constantly eating ram. Now it consumes 940 mb and keep going up. If I kill this process all open tabs crashes and afeter 30 sec plugin container restarting and continue rising mem usage from 100mb. Also it reads and writes disk at around 0.1Mb/s rate

Geändert am von ownageismagic

Ausgewählte Lösung

hi, when you are on pre-release you are probably using multiprocess firefox. all web content will run in the plugin-container.exe process in this case. https://wiki.mozilla.org/Electrolysis

Diese Antwort im Kontext lesen 👍 4

Alle Antworten (6)

ownageismagic
ownageismagic Fragesteller
more options

Here is screenshot

FredMcD
FredMcD
more options

Let’s do a full clean re-install; Download Firefox For All languages And Systems {web link} Save the file. Then Close Firefox.

Using your file browser, open the Programs Folder on your computer.

Windows: C:\Program Files C:\Program Files (x86) Mac: Open the "Applications" folder.
https://support.mozilla.org/en-US/kb/how-download-and-install-firefox-mac Linux: Check your user manual.

Do Not remove the profiles folder.

Look for, and rename any Mozilla or Firefox program folders by adding .old to them. Do not rename the Mozilla Thunderbird folder.

After rebooting the computer, run a registry scanner. Then run the installer. If all goes well, remove the OLD folders when you are done.

If there is a problem, start your Computer in safe mode and try again.

Starting The Computer In Safe Mode;
Free Online Encyclopedia

ownageismagic
ownageismagic Fragesteller
more options

FredMcD It doesn't help

philipp
philipp
  • Moderator
more options

Ausgewählte Lösung

hi, when you are on pre-release you are probably using multiprocess firefox. all web content will run in the plugin-container.exe process in this case. https://wiki.mozilla.org/Electrolysis

ownageismagic
ownageismagic Fragesteller
more options

philipp said

hi, when you are on pre-release you are probably using multiprocess firefox. all web content will run in the plugin-container.exe process in this case. https://wiki.mozilla.org/Electrolysis

Thank you for the answer. But why it leaking so bad? Calling GC from about:memory stips around 2 mb only. Killing process and reloading all tabs releases 300-500 mb

Geändert am von ownageismagic

philipp
philipp
  • Moderator
more options

that probably depends on the kinds of websites you are using. e10s is generally increasing the memory-footprint though: http://www.erahm.org/2016/02/11/memory-usage-of-firefox-with-e10s-enabled/