3 ms·
The "plugin-container" executable is used for all sandboxed processes on Windows. That started out as plug-ins, but now includes web renderers. So the "someth
by bzbarsky 8y ago
The "plugin-container" executable is used for all sandboxed processes on Windows. That started out as plug-ins, but now includes web renderers.
So the "something inside it" could be script on a web page, or part of Gecko's rendering pipeline, or pretty much anything. And killig it crashes tabs because it's the thing rendering those tabs.
It might make sense to rename the executable to make things clearer, but there are some problems: there is Windows software that hardcodes the executable name and does things based on it, and changing the name would break various things for users....
On Mac and Linux, where this problem doesn't exist, the process naming is much saner...
- Sharlin 8y agoOh, my experience was on Mac like the GP’s. Edited to clarify. On Windows or Linux I haven’t encountered a similar 100% CPU use problem, which has led me to suspect it’s specifically the Mac version of some plugin that’s the problem.
- bzbarsky 8y agoInteresting. On Mac, the process is called "plugin-container" if you use something like "ps", but Activity Monitor shows it as "FirefoxCP Web Content", which is a lot clearer...
- dblohm7 8y agoActually we only use plugin-container for NPAPI on Windows. I believe that MacOS was specifically the platform where we ran into problems.
- bzbarsky 8y agoThank you for the correction!