Join the AMA (Ask Me Anything) with the Firefox leadership team to celebrate Firefox 20th anniversary and discuss Firefox’s future on Mozilla Connect. Mark your calendar on Thursday, November 14, 18:00 - 20:00 UTC!

Om de ûnderfining foar jo te ferbetterjen is tydlik de funksjonaliteit dan dizze website troch ûnderhâldswurk beheind. Wannear in artikel jo probleem net oplost en jo in fraach stelle wolle, kin ús stipemienskip jo helpe yn @FirefoxSupport op Twitter en /r/firefox op Reddit.

Sykje yn Support

Mij stipescams. Wy sille jo nea freegje in telefoannûmer te beljen, der in sms nei ta te stjoeren of persoanlike gegevens te dielen. Meld fertochte aktiviteit mei de opsje ‘Misbrûk melde’.

Mear ynfo

Dizze konversaasje is argivearre. Stel in nije fraach as jo help nedich hawwe.

Plugin-container is a cpu hog. I need to end the program. Harmful?

  • 1 antwurd
  • 10 hawwe dit probleem
  • 10 werjeftes
  • Lêste antwurd fan the-edmeister

more options

Cpu usage is 100% due to plugin-container.exe

This happened

Every time Firefox opened

== Firefox update

Cpu usage is 100% due to plugin-container.exe == This happened == Every time Firefox opened == Firefox update

Alle antwurden (1)

more options

http://kb.mozillazine.org/Plugin-container_and_out-of-process_plugins ---

Try to disable IPC. You can set the prefs dom.ipc.plugins.enabled.* to false on the about:config page to disable the plugin-container process to see if that helps. dom.ipc.plugins.enabled.npswf32.dll (Flash) dom.ipc.plugins.enabled.npctrl.dll (Silverlight) dom.ipc.plugins.enabled.npqtplugin.dll (QuickTime)

To open the about:config page, type about:config in the location (address) bar and press the Enter key, just like you type the url of a website to open a website. If you see a warning then you can confirm that you want to access that page.

Double-click each of those prefs to toggle them to false, then restart Firefox.