Why is there a process called "plugin-container.exe" running all the time on my computer since v4?
I recently updated from v3 to v4. Now I notice there is constantly running this process "plugin-container.exe" on my computer and using between 3 and 10 % of my processor. I am not running youtube or whatsoever. 1) What is the function of this plugin-container.exe? 2) Why is it new in v4? 3) Can I shut it down? 4) Is it going to remain in next versions of Firefox?
Thank you for your answer.
Regards, Paul
Wszystkie odpowiedzi (10)
This has been used since Firefox 3.6.4 to isolate plugins from the rest of Firefox. The theory is if the plugin crashes, Firefox can still continue running with the other content. I don't think there are any plans to change back to a single combined program.
Okay thanks, but why is it since v4 consuming CPU time where this was not the case in v3?
I'm not familiar with the changes in that program. You would think that if you play the same media and keep the same tabs open, then you would get the same or at least very similar results for memory and CPU usage. Maybe I can do a comparison after hours.
It is a shame that the plugin container does not handle certain plugins well. Real media crash it.
@finitarry
Uhmm, Real Player isn't part of the Out-of-Process Plugins - only Flash, QuickTime, and Silverlight - AFAIK.
In Firefox 4 the plugin-container process is used for all plugins (dom.ipc.plugins.enabled is true)
Okay people, thank you all for your answers. I still don't get it why this process that is present since 3.6 or so, now suddenly in version 4 is consuming CPU all the time, but I do understand that there is nothing terribly wrong with my PC. Thank you!
Once you start a plugin site, the plugin-container process starts and remains active even if you leave the site. You probably just haven't noticed that before.
Ed,
The reason for the existence of the plugin container is to prevent plugins from crashing Firefox. If there are some plugins the container cannot handle, you are forced to use a helper application or make Firefox handle the plugin directly, bypassing the plugin container. Kind of defeats the purpose, right?
Zmodyfikowany przez finitarry w dniu
Which plugin(s) are using CPU time in the plugin-container process?
I would assume that once you close the tab that the process is no longer active and that there is no significant CPU time. Memory won't be released.
Using Delete browsing, search and download history on Firefox to clear cookies can also cause plugin-container processes to appear.