Firefox Plugin-container.exe Final Fix

Ok here is one big deal about firfox.

What most people don't realize is that there is a hidden option in firefox that is sucking up resources like CPU and RAM.

This extra option that firefox has added is hindering firefox's speed and efficiency.

Plugin-container.exe is the name of this problem.Most of use all ready know this but the ones that don't know it there is a way to disable this problem and still watch videos. With out an issue,This problem has been around since firefox 28 version and it still will cause an issue.

Where is why it will use the adobe flash or shockwave flash players this is where the problem starts.And you really don't need to use the flash player to watch a video or movie on the web browser.

I think that all the newer firefox versions have a new add on that beats flash player by miles and has not given me any issues.OpenH264 Video Codec works well and buffer's a lot faster than flash video.

Ok here come's the fun part of disabling Plugin-container.exe.

Below is how i use to do it the old way this still helps.

1.Open Firefox and type about:config and click I’ll be careful , I promise

2.Now search for dom.ipc in Filter box.

3.Double click on each of 3 entries below to set their values to false as.If you do not see the three lines be low you will have to enter them manually as boolean options and as false.

dom.ipc.plugins.enabled
dom.ipc.plugins.flash.subprocess.crashreporter
dom.ipc.plugins.reportCrashURL

4.You will have to add the 4 remaining items below.They will all so need to be Type Boolean for them to work.
Set each one to false.

dom.ipc.plugins.enabled.npctrl.dll
dom.ipc.plugins.enabled.npqtplugin.dll
dom.ipc.plugins.enabled.npswf32.dll
dom.ipc.plugins.enabled.nptest.dll

5.Restart Firefox browser.That’s it plugin–container is completely disabled for Firefox browser.

And if you do have flash installed i would disable it in firefox Add-ons manger.

If you see Shockwave Flash in your plugins section.I woud go to the right of it and click the Always active option and make it Never active.And only use the OpenH264 Video Codec works very well buffers the video better than flash and does not cause lag issues.

FYI you can see Plugin-container.exe in your task manger while you are playing a video with flash player when you do this it will be gone.

I hope this helps.

 

Been using all versions of Firefox from the start up to the latest and, apart from making sure flash is always up to date, and plug ins are set to 'ask to activate', I have never seen the problem you suggest.
Script automatically loaded in to millions of websites is what causes web browser slowness and plug in crashes. Using NoScript and extensions such as AdBlock Plus and uBlockOrigin work very well to limit such problems.
The number of times in over 10 years I have needed to go into about:config I could count on one hand.

 

If you look at reports this problem still happens to day,Most people don't see the issue.

 

Problems happen on systems all the time. Many problems are due to the state of the system itself rather than any inbuilt bugs in actual programs. If people don't 'see' a problem I assume that means they don't 'experience' a problem.
Please link directly to the reports of problems and link to the suggested fix.
As I say, I have been using Fx since it was called Phoenix and have been helping a significant number of people with system issues for the same time period, and I am not seeing the problem you propose in this thread and certainly not one that requires getting inside the bonnet of Firefox. I haven't seen any such suggestion on Mozilla Support or on Mozillazine. But if you can link me to posts there that support this action it would be great. That's my specific experience of using Firefox to view media.

 

This is most recent stuff about this problem.
https://support.mozilla.org/en-US/questions/1086196

Yes it may be a thread from october of last year but this problem still is a issue on many levels.And they pin point the issues.

 

It doesn't suggest the complex solution that you make. Nor does it even suggest the problem is the one you suggest.
Getting people to go into about:config for Fx or any other browser is a very rare requirement. It's dangerous - especially for people who simply don't maintain their system very well to start with.
The fact is, with the suggestions already made to many users here already - keeping flash up to date, always having it set to 'ask to activate' and using script limiting extensions works mostly fine.

 

From an old(2010) Fx forum thread:
http://forums.mozillazine.org/viewtopic.php?p=9530495#p9530495.
And from an old Mozillazine-kb article:
http://kb.mozillazine.org/Plugin-container_and_out-of-process_plugins.

They may be old but there they are.

 

No fixes requiring about:config changes in current versions of Firefox.
No reference at all to anything remotely described in post #1 here for common issues reported here, of which there are many threads.
Telling people to make the changes described is inadvisable.