We're calling on all EU-based Mozillians with iOS or iPadOS devices to help us monitor Apple’s new browser choice screens. Join the effort to hold Big Tech to account!

Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Plugin-container uses a lot of CPUtime.

more options

I like to keep a few tabs open to webpages I want to revisit or read later. So it is not uncommon for me to have 1 or two active pages I'm looking at, and 20 dormant pages I won't be looking at for a few days.

Since the last upgrade, the plugin-container is taking a lot of CPU time. (it might have been the firefox process before the upgrade, but it was less noticeable).

From the help for "plugin-container" I see that adobe flash is the only currently supported plugin. So, can I pause the flash on my inactive pages so that I can save some CPU time (and energy).


This happened

Every time Firefox opened

== I upgraded.

I like to keep a few tabs open to webpages I want to revisit or read later. So it is not uncommon for me to have 1 or two active pages I'm looking at, and 20 dormant pages I won't be looking at for a few days. Since the last upgrade, the plugin-container is taking a lot of CPU time. (it might have been the firefox process before the upgrade, but it was less noticeable). From the help for "plugin-container" I see that adobe flash is the only currently supported plugin. So, can I pause the flash on my inactive pages so that I can save some CPU time (and energy). == This happened == Every time Firefox opened == I upgraded.

All Replies (2)

more options

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

The currently supported plugins are NPAPI test plugin, Adobe Flash, Apple QuickTime (Windows) and Microsoft Silverlight (Windows)