Windows 10 reached EOS (end of support) on October 14, 2025. If you are on Windows 10, see this article.

Cari Bantuan

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.

Pelajari Lebih Lanjut

Disable 'plugin-container' in FF 17?

  • 5 balas
  • 22 memiliki masalah ini
  • 13 kunjungan
  • Balasan terakhir oleh cor-el

I've done it before with previous versions of FF but I forgot how. It's very simple, I want to disable this 'plugin-container.exe' and let the plugins run within the FF.exe thing.

The previous version I WAS (no italics) using I had it disabled. I clicked 'About FF' to figure out what version I was using and this farging thing just automatically updated and now I have to deal with this greedy plugin container.

So, I do this?

1: type in about:config 2: look for (need file/field names) 3: change certain fields to 'false'

Again, I just need the field names for 2 and 3. Please don't refer me to some useless link.

I've done it before with previous versions of FF but I forgot how. It's very simple, I want to disable this 'plugin-container.exe' and let the plugins run within the FF.exe thing. The previous version I WAS (no italics) using I had it disabled. I clicked 'About FF' to figure out what version I was using and this farging thing just automatically updated and now I have to deal with this greedy plugin container. So, I do this? 1: type in about:config 2: look for (need file/field names) 3: change certain fields to 'false' Again, I just need the field names for 2 and 3. Please don't refer me to some useless link.

Semua Balasan (5)

What a headache. Thanks for the useless link.

Which prefs do you currently have if you search for dom.ipc.plugins.enabled on the about:config page?

One more time...setting dom.ipc.plugins.enabled to false DOES NOT STOP PLUGIN CONTAINER!!!! Please stop giving this answer as a solution, Cor-el. It is simply wrong.

278   // On Windows Vista+, we force Flash to run in OOPP mode because Adobe
279   // doesn't test Flash in-process and there are known stability bugs.