Is Plugin-Conta Eating Up Your Memory? Here’s What It Is and What to Do About It

firefox slow as molasses
Share the knowledge

So your Firefox browser is slow as molasses or unresponsive, and in fact your entire system is slowing towards a screeching halt. If you’re on a Mac, you do a ‘top’ and see that a process called “plugin-conta” is eating up your memory. If you’re on a Windows machine, well, you know the symptoms. What is plugin conta, and what to do? Here’s what.

Plugin-conta is the truncated abbreviation for ‘plugin-container’. On Macs its full name is plugin-container.app, and on Windows machines it’s ‘plugin-container.exe’.

plugin-conta top plugin.conta

 

Plugin-container is Firefox’s fault. It is installed with Firefox, and used to run plugins within Firefox.

As Mozilla support wiz (and IP attorney) Jefferson Scher points out over on the Mozilla support site:

The Internet Patrol is completely free, and reader-supported. Your tips via CashApp, Venmo, or Paypal are appreciated! Receipts will come from ISIPP.

CashApp us Square Cash app link

Venmo us Venmo link

Paypal us Paypal link

…as the name implies, plugin-container.exe is used to run plugins. This was created around the time of Firefox 3.6.4 to isolate plugins from firefox.exe because they were responsible for a large percentage of Firefox crashes. Placing them in plugin-container.exe prevented misbehaved plugins from taking down your entire Firefox session (at least, in theory it should do that).

The bottom line is that Plugin-container, well, contains your plugins when they are running, in theory to protect your main Firefox instance from being taken down if a plugin causes issues. Of course, if the Plugin-container contained instance eats up all of your memory, causing your entire system to seize up (as has happened to us), then it really amounts to the same thing. But we digress.

So, what can you do about this? Well, if you are keen on keeping Firefox, then they suggest that you figure out which plugin is causing the issue by disabling your Firefox plugins, one at a time, until you figure out which one is the culprit. On the Firefox support site they say:

You can test to see whether one of your plugins is causing Firefox to use too much memory by selectively disabling some of them:

  • Click the menu button New Fx Menu and choose Add-ons. The Add-ons Manager tab will open.
  • In the Add-ons Manager tab, select the Plugins panel.
  • Click on a plugin in the list to select it, then select Never Activate to disable it.
  • Repeat {as needed} for some of the plugins in your list.

After disabling some of your plugins, close and restart Firefox, and observe its memory usage. If you don’t see an improvement, you can enable those plugins again and try with a different set.

If you do see an improvement in Firefox’s memory usage after disabling a certain plugin, you may leave it disabled. If you can’t because its use is widespread on Internet, try to find an alternative lighter plugin.

By far, the most likely culprit is Adobe Flash. So, before you do anything else, if you must use Flash, make sure that your Flash is up-to-date (but be sure to read this article first.

Get New Internet Patrol Articles by Email!

The Internet Patrol is completely free, and reader-supported. Your tips via CashApp, Venmo, or Paypal are appreciated! Receipts will come from ISIPP.

CashApp us Square Cash app link

Venmo us Venmo link

Paypal us Paypal link

 


Share the knowledge

Leave a Reply

Your email address will not be published. Required fields are marked *

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.