搜索 | 用户支持

防范以用户支持为名的诈骗。我们绝对不会要求您拨打电话或发送短信,及提供任何个人信息。请使用“举报滥用”选项报告涉及违规的行为。

详细了解

Plugin conatainer still eating ram without any plugins

  • 6 个回答
  • 34 人有此问题
  • 4 次查看
  • 最后回复者为 philipp

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

由ownageismagic于修改

被采纳的解决方案

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

定位到答案原位置 👍 4

所有回复 (6)

more options

Here is screenshot

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

more options

FredMcD It doesn't help

more options

选择的解决方案

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

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

由ownageismagic于修改

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/