why does the plug-in container "lock-up" or go into an infinite loop so often?
At random (apparently...) times, the "plug-in Container for Firefox (32 bit)" will either go into what appears (to this experienced programmer...) to be an infinite loop, or crash altogether. The website being displayed apparently doesn't matter, as long as it uses Flash or JAVA. I've had the problem with: Xfinity E-mail, Flickr, and this very support website. This is frustrating as all get-out, and is forcing me to consider going to Chrome as my primary Web-reader, when I've been a dedicated Firefox user since the single-digit versions...
All Replies (6)
Flash Player was just updated
Note: Windows users should download the active_x for Internet Explorer. and the plugin for Plugin-based browsers (like Firefox).
Note: Windows 8 and Windows 10 have built-in flash players and Adobe will cause a conflict. Install the plugin only. Not the active_x.
Flash Player Version: 23.0.0. 207 Flash Player (Linux) Version 11.2. 202.643
https://get.adobe.com/flashplayer/ Direct link scans current system and browser Note: Other software is offered in the download.
https://get.adobe.com/flashplayer/otherversions/ Step 1: Select Operating System Step 2: Select A Version (Firefox, Win IE . . . .) Note: Other software is offered in the download.
See if there are updates for your graphics drivers https://support.mozilla.org/kb/upgrade-graphics-drivers-use-hardware-acceleration
The computer giving me problems has Win 10 as the operating system...
FredMcD said
Windows 10 have built-in flash players and Adobe will cause a conflict. Install the plugin only. Not the active_x.
I haven't installed any Active-x, AFAIK...
There is another use for plugin-container.exe in the latest versions of Firefox:
e10s
One of the headline changes in Firefox 48-49 is e10s, which separates the browser interface process from the page content process (content processes move into plugin-container.exe). The performance impact of this can vary a lot between systems: many users find it faster, some find it slower, for many it's neutral. Hopefully by the time all the kinks are worked out it will work smoothly for everyone.
Are you using e10s?
You can check whether you have this feature turned on as follows. Either:
- "3-bar" menu button > "?" button > Troubleshooting Information
- (menu bar) Help > Troubleshooting Information
- type or paste about:support in the address bar and press Enter
In the first table on the page, check the row for "Multiprocess Windows" and see whether the number on the left side of the fraction is greater than zero. If so, you are using e10s.
If you are using e10s:
To help evaluate whether that feature is causing this problem, you could turn it off as follows:
(1) In a new tab, type or paste about:config in the address bar and press Enter/Return. Click the button promising to be careful.
(2) In the search box above the list, type or paste autos and pause while the list is filtered
(3) Double-click the browser.tabs.remote.autostart.2 preference to switch the value from true to false
Note: the exact name of the preference may vary, but it will start with browser.tabs.remote.autostart
At your next Firefox startup, it should run in the traditional way. Any difference?