X
Tryk her for at gå til webstedets mobilversion.

Supportforum

Jan: plugin-container use monster memory

Skrevet

container is monster hungry. Use more memory than fox does. more than 2 time of total memory use by container rather than by fox.

container is monster hungry. Use more memory than fox does. more than 2 time of total memory use by container rather than by fox.

Yderligere systemdetaljer

Installerede plugins

Default

Program

  • User Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.2) Gecko/20100316 Firefox/3.6.2

Yderligere information

Already disable container. Seems fox still slow to no respond. Must click a few times but sometime seems slow to respond. So decide to remove latest update. Restart and install older version 3.6.2. Everythings seems ok. Almost forget to disable auto update. Maybe in the next future i will use new version.

Luk
Morbus 135 løsninger 2340 svar

Hello alongeasy.

The plugin container is meant to use as much memory and CPU power as the plugins need. In basic terms, any memory and CPU cycles used by the plugin container would have been used by Firefox itself in previous versions. So you have to judge if the amount of RAM and CPU taken by the container is disproportionate to the amount of RAM and CPU take by Firefox in previous versions.

That said, you shouldn't need to have any sort of technical knowledge to judge this, and you shouldn't have to worry about the technical details at all. If the plugin container is consistently using up RAM above 50MB or 100MB, that's most likely a problem. However, it's most likely to be a problem with an add-on (probably one of the plugins in use) rather than Firefox. Run Firefox in safe mode, select Disable all add-ons when you start safe mode and see if the problem disappears. If they do, you know it's from an add-on. Disable them all in normal mode, and enable them one at a time until you find the source of the problem. See this article for information about troubleshooting extensions and themes and this one for plugins.

If you need support for one of your add-ons, you'll have to contact its author.

If the problem is not disappears when all add-ons are disabled, please tell me, so we can work from there. Please have no fear of following my instructions to the line, as all can be easily undone.

Hello alongeasy. The plugin container is meant to use as much memory and CPU power as the plugins need. In basic terms, any memory and CPU cycles used by the plugin container would have been used by Firefox itself in previous versions. So you have to judge if the amount of RAM and CPU taken by the container is disproportionate to the amount of RAM and CPU take by Firefox in previous versions. That said, you shouldn't need to have any sort of technical knowledge to judge this, and you shouldn't have to worry about the technical details at all. If the plugin container is consistently using up RAM above 50MB or 100MB, that's most likely a problem. However, it's most likely to be a problem with an add-on (probably one of the plugins in use) rather than Firefox. Run Firefox in [http://support.mozilla.com/en-US/kb/Safe+Mode safe mode], select ''Disable all add-ons'' when you start safe mode and see if the problem disappears. If they do, you know it's from an add-on. Disable them all in normal mode, and enable them one at a time until you find the source of the problem. See [http://support.mozilla.com/en-US/kb/Troubleshooting+extensions+and+themes this article] for information about troubleshooting extensions and themes and [https://support.mozilla.com/en-US/kb/Troubleshooting+plugins this one] for plugins. If you need support for one of your add-ons, you'll have to contact its author. If the problem is not disappears when all add-ons are disabled, please tell me, so we can work from there. Please have no fear of following my instructions to the line, as all can be easily undone.
disasterman 1 løsninger 10 svar

Nyttigt svar

I have consistently had this problem with just about every release of firefox, and can tell you that the plugincontainer.exe file is the culprit, not addons. I have run Fox stripped of addons and had the same exact problem. When I go in to the configuration settings and change the values to false to prevent it loading, and (on mine anyway) set the timeouts to 10 seconds, it cleared the problem up.

Many others have said the same thing.

So my question is, why doesn't firefox just get rid of plugincontainer.exe? DUH!

My firefox 9.0.1 works fine with it disabled.

I have consistently had this problem with just about every release of firefox, and can tell you that the plugincontainer.exe file is the culprit, not addons. I have run Fox stripped of addons and had the same exact problem. When I go in to the configuration settings and change the values to false to prevent it loading, and (on mine anyway) set the timeouts to 10 seconds, it cleared the problem up. Many others have said the same thing. So my question is, why doesn't firefox just get rid of plugincontainer.exe? DUH! My firefox 9.0.1 works fine with it disabled.
Yvda1973 0 løsninger 3 svar

It's NOT the add-ons, its NOT the themes, It's the plugin-container ITSELF that eats up memory like a bear after wintersleep!!

It's NOT the add-ons, its NOT the themes, It's the plugin-container ITSELF that eats up memory like a bear after wintersleep!!