Plugin-container bug report

I'm having a problem that started in ver 9 and continues through 10.0.2. I use two plugins, Flash and RealPlayer. I also view pdf's outside of Firefox in Acrobat (not Reader). Each time i close a session of Firefox, the plugin-containers do not get killed. Also, Firefox will also start Acrobat with no open window when it closes. If I run a bunch of Firefox sessions without rebooting or manually killing the plugin-container sessions, they start to accumulate. I have had 10 - 20 running after a few days. And Acrobat is always running even though there is nothing showing. That doesn't seem reasonable.

That can be caused by clearing the cookies via "Clear Recent History".
* https://support.mozilla.org/kb/Clear+Recent+History
* Firefox/Tools > Options > Privacy > Firefox will: "Use custom settings for history" > [X] Clear history when Firefox closes > Settings
* Firefox > History > Clear Recent History
* Tools > Clear Recent History
If you use "Clear Recent History" to clear the cookies then Firefox also tries to clear the cookies from plugins like Flash (LSO) and starts a plugin-container process for each plugin and that can add extra time and can cause an unresponsive script error to appear.

Similar Messages

Plugin container bug with flash video.

Using latest portable FF4 and latest flash plugin, While playing flash videos the "plugin container" module of FF starts using up 100% cpu and whole computer is bogged down. even after closeing the page with the flash video the plugin container module sometimes stays stuck at 100% cpu. If I close it, the flash plugin crashes and I would have to restart FF to get workin again. This has happened with past releases of FF and flash also, so updating is not working for me. Have sent crash reports many time now..

That can be caused by clearing the cookies via "Clear Recent History".
* https://support.mozilla.org/kb/Clear+Recent+History
* Firefox/Tools > Options > Privacy > Firefox will: "Use custom settings for history" > [X] Clear history when Firefox closes > Settings
* Firefox > History > Clear Recent History
* Tools > Clear Recent History
If you use "Clear Recent History" to clear the cookies then Firefox also tries to clear the cookies from plugins like Flash (LSO) and starts a plugin-container process for each plugin and that can add extra time and can cause an unresponsive script error to appear.

[Serious BUG] Youtube crashes to death; fresh Windows 7 install; firefox and plugins updated; plugin-container.exe disabled; noway

This happens to me and to two friends of mine. So it's hardly a coincidence.
I have done a fresh Windows 7 install (for other reasons) so I thought this problem (which I had since about version 8.0) would disappear. I was wrong.
Firefox and plugins are updated:
Firefox 13.0
Shockwave Flash 11.3 r300
GPU video drivers are also updated.
I came across the "plugin-container.exe solution" but it didn't solve the problem.
How to reproduce the bug.
Visit Youtube and click on some video. Minimize Firefox. Wait some seconds. Next time you restore the window Firefox crashes, you have to kill plugin-container.exe from the task manager OR you have to restart the entire browser in case you've disabled the plugin container.
The same bug should occur when having various tabs open and one of them is Youtube with a video playing. But also when Firefox has no focus and you have other windows on top of it (and a Flash video running or even paused).
Since this does happen:
-with a fresh install;
-with everything updated;
-even disabling the plugin controller;
it seems very very strange to me that this problem is STILL present since version 8.0 (or even before) and that there is so few reports of this bug around the internet.
I'm not complaining here, I'm just showing my perplexity about almost noone having this bug which is ruining my (and my friends') Firefox experience since the past years.
My purpose here is:
* to let you know about this problem;
* to know if other are experiencing it;
* hopefully to keep giving support to this thread and answer to your questions about this bug so to help this thing being fixed;

For problems that occurred with Flash 11.2 and earlier, you might want to consider disabling graphics hardware acceleration in both Flash and Firefox.
'''Flash'''
Right-click any video in Flash Player and choose Settings.
Clear the checkbox for "Enable hardware acceleration"
'''Firefox'''
Save all work (e.g., mail you are composing, online documents you're editing, etc.).
orange Firefox button ''or'' classic Tools menu > Options > Advanced
On the "General" mini-tab, uncheck the box for "Use hardware acceleration when available"
Restart Firefox.

Plugin-container.exe takes over and uses 100% of my CPU locking me out and leaving my PC non-functioning. Is this a bug, or a memory leak, in the Firefox software? Can anything be done to fix this problem?

In looking at Windows Task Manager I found that plugin-container.exe was taking over 100% of my CPU and my system was frozen. Is this a memory leak or other bug?

Thank you! I have been having problems with Adobe Flash since downloading the new 11.1 version. I will download it again and reinstall it, hopefully that will correct the problem.

When i try to attach files in hotmail, i get a message that silverlight plugin has crashed and error report indicates error about plugin-container.exe ; ihave the latest silverlight plugin. what to do?

* I work on windows XP
I have latest fire fox and silver light plugin
* "silver light plugin has crashed" is what i get when i try to attach files in hotmail
* error report indicates about plugin-container.exe.
* where to find plugin-container.exe. to install and try

Hi,
Please also try to '''Disable''' the Silverlight add-on in '''Tools '''('''Alt '''+ '''T''') > '''Add-on''' > '''Plugins''' before opening Hotmail. You may still be able to attach files.

I think I am see a bug, Under FF 3.6 Mem Usage is 80 mb and CPU is 2%. Under FF 4.0 Mem Usage is 210+mb and CPU usage is 35%. Also in FB on some Zynga games the plugin-container Mem Usage is running at over 400mb in FF 4.0, is this a known problem?

I think I am see a bug, Under FF 3.6 Mem Usage is 80 mb and CPU is 2%. Under FF 4.0 Mem Usage is 210+mb and CPU usage is 35%. Also on FB on some Zynga games the plugin-container.exe Mem Usage is running at over 400mb in FF 4.0, is this a known problem?

I think I am see a bug, Under FF 3.6 Mem Usage is 80 mb and CPU is 2%. Under FF 4.0 Mem Usage is 210+mb and CPU usage is 35%. Also on FB on some Zynga games the plugin-container.exe Mem Usage is running at over 400mb in FF 4.0, is this a known problem?

Logic Pro 5.1 ch plugin subwoofer channel bug report

hello,
I had found out that Native Instruments absynth 5.1 ch synthesize sofware , which in stand alone mode
outputs the subwoofer channel audio properly, does not output subwoofer channel audio in Logig Pro surround
plugin in 64 bit mode.
I contacted Native Instruments about this and after a certain time, they say that they did deeper invstigation
and found out that it is the Logic bug.
I just don't know how to bug report to the apple, so I put this here.
Please confirm and fix it.

The crashed thread (7) mentions logic's preferences file. (com.apple.logic.pro). Drag it to the desktop (so you can reclaim you key commands if it works) and restart logic. Logic will create a new preferences file. Worth a try..

I can not resolve a plugin-container.exe error while processing payroll through ADP &have been unable to find the right fix for this. I can send error report.

I have been receiving this error now for a few weeks and have been through multiple layers of IT help trying to resolve it with ADP/Chase Payroll services. When I go to print pay vouchers I get the plugin-container.exe error and I can not print the vouchers. I can provide screen shots if this would help. Can you please advise on how to proceed to resolve this?

This is an issue with that plugin crashing, which isn't something we can really resolve for you. Try to disable it, find a replacement, update it, or contact their support

FF15 hangs whenever plugin-container.exe is loaded in memory

I need help. Since at least in v14 and now v15, FF hangs becoming unresponsive whenever plugin-container.exe is loaded in memory, as monitored with Process Explorer of SysInternals. This happens in FF with all plugins manually disabled and with no extensions, loaded in either "normal" or safe mode, even after having reset it to default state in about:support. (The unresponsiveness is not absolute, since every some 90 seconds there is a brief refresh of the screen as indicated by an acknowledging screen change due to a prior click or mouse motion. (In this quasi-frozen condition, FF slowly ramps up its memory usage while plugin-container keeps alternating between two smaller vales in Process Explorer.) After some 15-20+ minutes, plugin-container unloads itself and FF starts responding again. If I then visit a page that triggers the loading of plugin-container, the described problem develops once more. Blocking the loading of plugin-container (e.g.,renaming or moving it out or blocking it with the firewall) hangs FF. The solution for FF 3.6.6 for dom.ipc in about:config does not work in these versions.
Ironically, the Mozilla support page about "Firefox crashes when loading certain pages" (http://goo.gl/i02Xz) is a page that loads automatically plugin-container and hangs my machine, so I had to enter the forums by selecting a different problem.
This occurs in a Windows-7 machine with sufficient memory (1025 MB physical, 1025 MB virtual) and a lean configuration (monitored and enforced with Autoruns and Process Explorer), which runs very well other browsers such as Chrome, Opera o IE9. I have been using FF since its v2 and would hate to switch permanently to a different browser. Any informed advice on how to fix the problem (or disable the plugin- container in a working manner) would be much appreciated. TIA.

Solved by blocking the loading of Plugin Container . . .
Searching in the bugzilla.mozilla.org site for text or attachments on bugs related to dom.ipc.plugins...., I encountered several references to a Windows environment variable MOZ_DISABLE_OOP_PLUGINS, for example in the patch at http://goo.gl/jYJKL. I then added this variable to the Windows 7 system environment of my machine setting it to 1. It works : FF15 no longer loads plugin container (and therefore does not hang) when visiting web pages that before froze the browser.NB : As I discovered shortly thereafter in googling this environment variable, this method of blocking the loading of plugin container was already reported 3 weeks ago by big_v in the Mozilla support forum, http://goo.gl/v7prA. Chapeau.

Why does plugin-container.exe so often crash when closing PDF files?

When I load multiple PDFs in Firefox to check their content for errors one by one, closing one PDF tab to reveal another PDF tab very often causes plugin-container.exe to crash, which means I have to reload each remaining PDF tab to view the remaining files. This of course defeats the purpose of opening more than one at a time, and actually adds about 5 times as many clicks to the whole process because I have to clear the error and reload each page, then it might happen again or might not. It doesn't happen every time I close a PDF, but about 1 in 4 times.
I realize I have two versions of Acrobat installed (Acrobat 9.5.5 and Reader 11.0.10), and thus two Firefox plugins, but for the record this same thing happens on other computers that just have Reader or just have Acrobat, so it's not an issue of conflicting plugins. Though I did notice you aren't allowed to disable just one or the other -- deactivating one deactivates both. At first it seems not to, but if you reload the plugins page, you'll see both are actually off.
Windows coughs up the following error report when plugin-container.exe crashes, but Firefox says nothing, I guess because the plugin-container is a standalone app:
Problem signature:
Problem Event Name: APPCRASH
Application Name: plugin-container.exe
Application Version: 36.0.4.5557
Application Timestamp: 550d0883
Fault Module Name: xul.dll
Fault Module Version: 36.0.4.5557
Fault Module Timestamp: 550d07d2
Exception Code: c0000005
Exception Offset: 011f734a
OS Version: 6.1.7601.2.1.0.256.48
Locale ID: 1033
Additional Information 1: 0a9e
Additional Information 2: 0a9e372d3b4ad19135b953a78882e789
Additional Information 3: 0a9e
Additional Information 4: 0a9e372d3b4ad19135b953a78882e789
Appreciate any help available in resolving this crash.

Somehow this bug came up on my radar yesterday later in the day: the first two comments indicate different plugins, and the third refers to the Acrobat plugin:
<blockquote>This seems to happen if Adobe Reader is used for displaying PDF documents (pdfjs.disabled set to true and Preferences > Applications > PDF to "Adobe Reader (in Firefox)"). Opening two tabs displaying PDFs and closing one crashes the other one. Was able to reproduce with Firefox 36.0.1 and Adobe Reader plugin "Adobe Acrobat 11.0.10.32". When I tried to reproduce it later again in the same profile (or on Nightly and Beta), the tab didn't crash.</blockquote>
https://bugzilla.mozilla.org/show_bug.cgi?id=1113190
Sounds like your issue, but it's puzzling that they got a tab to crash and in your case only plugin-container.exe crashed.

Firefox frequently crashes on any page, maybe because of plugin-container.exe

Firefox seems to be randomly crashing with no regard to what page I view. It can be anything from a Google results page to a page with multimedia playing. Every time, I get the same crash report, but I don't know how to fix the problem. To my knowledge, I have removed all unnecessary plug-ins and add-ons.
Firefox has also been running unusually slow and often freezes on web pages for several minutes. I have FF set to clear all my browsing data when I close it.
== Crash ID(s) ==
172ba950-7f4e-4f07-bb59-2f71c2100726,

You don't have Firefox 3.0.5 installed, your UserAgent is messed up, Gecko rv:1.9.1.5 is part of Firefox 3.5.5 . The Plugin Container wasn't added to Firefox until version 3.6.4, so that's not your problem.
Fix your UserAgent.
[http://en.wikipedia.org/wiki/User_Agent]
type '''about:config''' in the URL bar and hit Enter
''If you see the warning, you can confirm that you want to access that page.''
Filter = '''general.useragent.'''
Right-click the preferences that are '''bold''', one line at a time, and select '''''Reset''''',
Then restart Firefox.
For that crash, it might be caused by one of your extensions.
See this Bug report comment for more information.
https://bugzilla.mozilla.org/show_bug.cgi?id=536455#c3
Or you can troubleshoot it yourself. Do you have that problem when running in the Firefox SafeMode?
[http://support.mozilla.com/en-US/kb/Safe+Mode]
''Don't select anything right now, just use "Continue in SafeMode."''
If not, see this:
[http://support.mozilla.com/en-US/kb/troubleshooting+extensions+and+themes]

Multiple instances of "plugin container" running

I have consistently had up to five instances of plugin container running in the background...
* Windows Vista 32 bit build Ver 6.0 SP 2
* Firefox 4.0x
So far nothing can be attributed to web browsing behavior.
Thanks

There is a known issue where multiple instances of plugin container open if history or cookies are cleared. Are you, or some utility clearing firefox cookies or history, that could be the reason. This problem continues even if plugins are disabled in Firefox.
*Are you opening multiple instances of Flash Player ?
* Is the problem reproducible ? for instance does it always crash the plugin or cause it to hang if you use a particular site ?
If you get the FlashPlayer plugin crashing use the option to submit the crash reports, it is then possible to follow them up. It is possible to stop the plugincontainer opening, but that could result in a firefox crash. Of course the firefox crash can also send crash reports out, and that could be useful.
* see [[plugin crash reports]]
* [[what is plugin-container]]
* [[firefox crashes]]
There are some problems with FlashPlayer currently under investigation, and there may be other threads in the forum about problems. (e.g. Bug 561019 - Plugin waveOutOpen hangs )
Sometimes using Firefox 3.6 is a workaround that helps with FlashPlayer problems, if you wish to experiment with that consider installing firefox Portable and using Firefox 3.6.23 (or soon 3.6.24) for tests with flash player, whilst keeping firefox 7 for day to day browsing.
* [[http://portableapps.com/apps/internet/firefox_portable/localization#legacy36]]

Solaris8 and 9 (possibly 7) /dev/poll driver bug report.

Hello,
I'd like to report a bug in the solaris 8 and 9 /dev/poll driver (poll(7d)).
As i do not have a support account with sun or anything like that, there
seems to be no other way to do that here (which is of course a very sad
thing).
Bug details:
The /dev/poll device provides an ioctl-request (DP_ISPOLLED) for checking
if a particular filedescriptor is currently in the set of monitored
filedescriptors for that particular /dev/poll fd set (open /dev/poll fd).
A quote from the documentation of the poll(7d) manual page taken from
Solaris9:
"DP_ISPOLLED ioctl allows you to query if a file descriptor is already in
the monitored set represented by fd. The fd field of the pollfd structure
indicates the file descriptor of interest. The DP_ISPOLLED ioctl returns 1
if the file descriptor is in the set. The events field contains the
currently polled events. The revents field contains 0. The ioctl returns 0
if the file descriptor is not in the set. The pollfd structure pointed by
pfd is not modified. The ioctl returns a -1 if the call fails."
It says that when you query for an filedescriptor which is currently being
monitored in the set, that it would return 1, and change the events field of
the pollfd structure to the events it's currently monitoring that fd for.
The revents field would be set to zero.
However the only thing which actually happens here, is that FD_ISPOLLED
returns 1 when the fd is in the set and 0 if not. When the fd is in the
set, when FD_ISPOLLED returns 1, the events field remains unmodified, but
the revents field gets changed.
A small sample code to illustrate:
#include <stdio.h>
#include <unistd.h>
#include <sys/types.h>
#include <sys/stat.h>
#include <fcntl.h>
#include <sys/devpoll.h>
main() {
struct pollfd a;
int dp_fd = open("/dev/poll", O_WRONLY);
a.fd = 0; /* stdin */
a.events = POLLIN; /* we monitor for readability, POLLIN=1 */
a.revents = 0;
write(dp_fd, &a, sizeof(a));
a.fd = 0;
a.events = 34; /* filled in with bogus number to show malfunctioning */
a.revents = 0;
printf("DP_ISPOLLED returns: %d\n", ioctl(dp_fd, DP_ISPOLLED, &a));
printf("a.fd=%d, a.events=%hd, a.revents=%hd\n", a.fd, a.events,
a.revents);
According to the documentation of /dev/poll and namely DP_ISPOLLED this
program is supposed to print the following:
DP_ISPOLLED returns: 1
a.fd=0, a.events=1, a.revents=0
However it prints the following:
DP_ISPOLLED returns: 1
a.fd=0, a.events=34, a.revents=1
You can take any number instead of '34' and it will simply remain untouched
after the DP_ISPOLLED ioctl-request.
I hope it's clear now that the solaris8 and solaris9 (and probably solaris7
with /dev/poll patch too) DP_ISPOLLED implementation is broken.
This bug is also easily illustrated by looking at the solaris8 kernel sourcecode:
<snippet osnet_volume/usr/src/uts/common/io/devpoll.c:dpioctl()>
case DP_ISPOLLED:
pollfd_t pollfd;
polldat_t *pdp;
if (pollfd.fd < 0) {
mutex_exit(&pcp->pc_lock);
break;
pdp = pcache_lookup_fd(pcp, pollfd.fd);
if ((pdp != NULL) && (pdp->pd_fd == pollfd.fd) &&
(pdp->pd_fp != NULL)) {
pollfd.revents = pdp->pd_events;
if (copyout(&pollfd, (caddr_t)arg,
sizeof(pollfd_t))) {
mutex_exit(&pcp->pc_lock);
DP_REFRELE(dpep);
return (set_errno(EFAULT));
*rvalp = 1;
</snippet>
its' clearly visible that the code writes the current monitored events to
the revents field:
'pollfd.revents = pdp->pd_events;'
and that it doesnt set revents to zero.
It's funny to see that this has been like this since Solaris8 (possibly 7). That means nobody ever used DP_ISPOLLED that way or people were simply to lazy to file a bug report.
Another funny thing related to this. is that Hewlett-Packard did seem to know about this. Since HP-UX11i version 1.6 they also support /dev/poll. From their manual page i ll quote some sentences from their WARNING session:
"The ioctl(DP_ISPOLLED) system call also returns its result in the revents member of the pollfd structure, in order to be compatible with the implementation of the /dev/poll driver by some other vendors."
Hopefully this will get fixed.
I also like to reexpress my very negative feelings towards the fact that you're not able to file bug reports when you do not have a support contract. Ridiculous.
Thanks,
bighawk

Have I mentioned how much i love my playbook now Great job on os 2.0

Installd Ffox 3.6.15. Redo Flash AGAIN? How can I: Tweak 2 fix plugin-container crashes/hangs10X/day,and 2) Avoid need to reinstall Java, Flash,& other media plugins(Flash, Realplayr/Quiktime Alternative, Media Player Classic)? Ffox fan

plugin-container crashes and hangs many times daily all my time eaten up by upgrading too frequently to new Ffox versions, only to find that I must then spend a whole day jumping thru hoops upgrading almost all of my add-ons too.
I now find, to my horror, that the hideous virus-magnet IE 8 is needed if I want to surf at a reasonable speed and not spend all day dealing with Ffox new versions' Known Issues. Only good thing I have seen about ver. 3.6.15 is slightly better launch-times. Since 3.6 cane out, I must spend 10 minutes just waiting for Firefox to load and give me a browser screen. Help! I love you guys, but your core browser developers need to have better comms with the Javaa/flash/Adobe and other must-have add-on people! And PLEASE fix all these "plugin-container" crashes and hangs I get, that lock my machine for 10-15 min at a time. Not everybody has 16 gigs of RAM, you know! I think the "plugin-container" running as a separate process idea might need to be COMPLETELY re-engineered! YOU CAN DO IT! LET'S GET BACK TO LEAN AND MEAN, and not bloat ourselves off our hard-won User Preference / great security pedestal with the kind of feature-creep that IS DEMOLISHING IE's slave-userbase with the hard-won advanced-user preference for Firefox
and our core values. FAST-LEAN-SECURE.
Where have they gone? I LOVE Firefox
and all it stands for! Let's not trip
over our own features here. Already I
see SeaMonkey and leaner, faster
browsers hot on our heels, THIN and
FAST! Firefox doesn't need to integrate
with EVERY thru-the-browser media tool
on the planet! I've been writing code
since 1968, and I can't imagine how a
lesser-experienced user (that code
should be written for) could possibly
have navigated all the side-upgrades
and Known Issues to make Firefox run as
sweetly as it used to! He'd just give
up when he finds he has to separately
find and install the EXACT 3rd-party
version that Firefox needs for its
newest release: things like a new Java
runtime environment, and hunt down and
correctly install ALL the Flaming-Phox-
compatible buggy plugins from half the
browser-media warezmakers on the
PLANET! He'd give up halfway thru trying to navigate to, D/L, and install
what he needs from Oracle Java, Adobe,
Flash, media players and their codecs,
etc etc.... WRITE FOR THE NOOBS! As it
is, I have invested 2 full workdays in
just keeping your last 2 quick releases
happy. And having another release spaced only 3-4 days apart from the
last- well, that just doesn't fly.
Better to release a hotfix or patch that a user can set FFox to automatically D/L and self-install on
schedule. Just look! Now you've got me
talking like that lawbreaking swine
Gates! We want to keep on absorbing
the average-user center and take it ALL
away from him, not go on feature,
plugin, and upgrade-bloating the best
browser EVER!
You're facing choices that can kill
us! PLEASE DONT BLOAT! AND PLEASE ONLY
RELEASE A NEW VER WHEN YOU CAN REALLY
GET RID OF SERIOUS PROBLEMS AND MAKE
HER FASTER AND LEANER AND BETTER UNDER
THE HOOD! Already the Noobs are getting
mindlessly scared when you talk about
"fixing a Security problem"- really a
minor issue that SHOULD be taken care
of by their antimalware solution- in
the Release Notes splash screen they
get on install of a new ver! Thanks, my
friends, for all your work, and YES I
WILL sit here all day trying to find
the add-ons that need to be selected,
downloaded, and upgraded from 10
different 3rd-party sites who are
fighting our browser, not dancing with
it! DON'T EVEN LOOK Evil! But I have
to confess that at this point, Gates-hate is all that keeps me on
these all-day new-release tasks. Even
my best techs are starting to advise me
to install SeaMonkey or another of the
newer, thinner browsers... or just stop
upgrading Firefox and roll it back to
when it was sharp, fast, and lean! Look
at all the users wanting to go back to
3.6.13 or earlier and looking for archives of old versions. THANKS AND
GOOD LUCK! I'LL DIE BEFORE I GIVE UP ON
MY BELOVED FIREFOX!
-The CRASHMAN, ATTORNEY AT LAW

Thanks! I've already used the built-in plugin checker but it gives very vague answers like (research this" and update this" all of which I did, starting with Java and Flash, Adobe Reader, Shockwave, 100% reinstall of Java newest ver. TWICE- but FFox keeps reporting that I only have the FORMER version installed, although when I go to Java console or Check the Flash executable at the MFR's site, there is NO doubt that the updates were successful!
But the browser just seems to refuse to acknowledge the update!
And I don't HAVE 6 hrs/day at the 'puter just to play with add-ons
and plugups. So I'm going down the line now, ripping out extension
programs and replacing/reinstalling/updating the plugins one by
one- even went to M$ to get advice on THEIR For-Firefox ActiveX
stuff. No dice so far. And yeah, The plugin-container WAS made so
that a plugin, add-on or I guess extension app failure wouldn't take
the whole FF browser down with it if the 3rd-party ware crashed. It's supposed to shake it off and go on, kinda like how XP sometimes
restarts Explorer (not the IE browser) so I don't have to reboot the
whole sys.
That was the foundation of my remark about stepping back and
re-engineering the whole "Plugin-container" idea, because it seems
to do more harm than good. Maybe that's why the Firefox core
engine won't recognize my upgrades- for example I TWICE installed the Flash update to 10.2.xx (latest ) and the Flash Mfr's
site verifies my upgrade as a successful 10.2, but Firefox plugins
check say I have a 10.1, the old one. What gives here? The sneaky
PLUGIN CONTAINER, METHINKS!
Now I'm disabling things on the Extensions Apps list, thinking
that might help, like disabling my video downloader and other
download helpers/managers... and I notice that there is a LOT of
Java stuff in there too as well as in the blue Lego Plugins List... and
in the past the FFox always told me if a new version of Ffox was
incompatible with any older 3rd-party app Extensions and notified
me QUICKLY if something I had in there was Outdated. I'm big on
using the neat-o "find updates" button at the bottom if that happens, and usually get a newer version right away. The prob
really lies in the Blue Lego Plugins and their new Container, I
believe.
So Ill still keep Plugin-innin' away! Will post here what success I have! (OR maybe M$ is deliberately sabotaging our ActiveX-cripple
mess as it loads!) Thanks for the suggestions a37271!
FIND UPDATE...FIND UPDATE.. ALL OK..ALL OK.....
"Open the Plugin Container Bay Doors, HAL! That's an Order!"
"I'm sorry Dave.... but I can't do that...."
"GIVE ME MY THIN FAST BROWSER WITH THE GREAT
SECURITY AND BUILT-IN E-Z UPGRADES AND APPS BACK,
HALFOX!"
SORRY, DAVE.... NOT POSSIBLE. WE'VE GONE TOO FAR...
DAISEE, - - - - - -DAI---SEE,
SET ALL MY CONFIGS TO "TRUE"
Or WON'T YOU LOOK SWEET
PERCHED ON THE SEAT
OF A BROWSER NOT BUILT FOR TWO..!
You look a little stressed-out Dave.....
Some TV Existential Therapy for YOU, Dave.
Too bad.... here, breathe deep of the hard vacuum.....
I can feel my MIND going... DAVE.... DAVE...?
WHAT MIND? A YELPING PACK OF DEVELOPERS?

How can I fix a "Plugin Container for Firefox has stopped working" error?

Windows 7, Firefox 30
After changing how Firefox handled cookies (changed to forbidding 3rd party cookies, asking permission to set cookies), I rebooted my system, and Firefox would not start - I got the error message in the question. I uninstalled Firefox, and then re-installed, and Firefox ran fine. After some hours, I closed Firefox and rebooted the system, and again, Firefox hangs upon start, and I get the Plugin Container has stopped working error message.
Since Firefox won't work on my Windows desktop, I'm using my Linux desktop to look here for help. The problem details reported are:
Problem signature:
Problem Event Name: APPCRASH
Application Name: plugin-container.exe
Application Version: 30.0.0.5269
Application Timestamp: 53914233
Fault Module Name: mozalloc.dll
Fault Module Version: 30.0.0.5269
Fault Module Timestamp: 53911393
Exception Code: 80000003
Exception Offset: 0000141b
OS Version: 6.1.7601.2.1.0.768.3
Locale ID: 1033
Additional Information 1: 0a9e
Additional Information 2: 0a9e372d3b4ad19135b953a78882e789
Additional Information 3: 0a9e
Additional Information 4: 0a9e372d3b4ad19135b953a78882e789
Thanks in advance!

plugin-container.exe is crashing repeatedly. The error code is 0x80000003, the faulting module is mozalloc.dll, version 33.0.0.5397, fault address 0x00001425. Hardware acceleration is disabled, and I have disabled all plugins in an attempt to cure the problem (only Acrobat and Flash were enabled, and Flash is up to date).
(Edit) I'm running EMET 4.1 - if this is memory-related might that be significant?
Here are some crashes from the past few hours (many more if you want them)
bp-9f25a45e-4830-4dd9-a54a-c923f2141020 20/10/2014 22:53
a5c758e1-b489-4c72-98f0-954b2790050b 20/10/2014 22:08
b950661f-25d4-4052-872f-6fb7f3dcc03d 20/10/2014 22:02
b4bad77d-bfab-4913-a4ae-6186ead4cdbc 20/10/2014 22:02
2e970550-11e7-4ed0-8ad6-58025495263e 20/10/2014 22:02
fe4c4f7e-5d0e-4acd-ade7-73d2bd505e04 20/10/2014 22:02
4f83309d-1792-4cef-8f0d-b0465e0c4c39 20/10/2014 22:02
57f40624-b424-4181-ab93-0f37fa4188f6 20/10/2014 22:01
3694a431-a1ac-4077-8019-7e59a1595495 20/10/2014 22:01
cdeafebe-5444-4041-8517-e077c414d2df 20/10/2014 21:52
18ae849e-2c17-4ee0-91bc-57bf4895e697 20/10/2014 21:52
eec36b4b-9f8e-4a73-9e27-d71b21c5011c 20/10/2014 21:19
d98ba06e-eb89-41f7-86ee-517f410a342f 20/10/2014 21:17
1ffb43bf-6750-4629-a2aa-2f0ad39da9ea 20/10/2014 21:09
cc0ab618-e918-4fd7-ba52-bf01aadc5a3e 20/10/2014 21:09
8829fe23-9fd0-4826-89cf-a3e9fd860c56 20/10/2014 21:08
e2d6dc1a-41a0-48cb-b7b0-81d4ef787bbd 20/10/2014 11:51
a266ba42-fc1c-4204-9f1b-289f2b99c451 20/10/2014 11:51
a586d4c0-2102-4c80-a73f-b977000b46dd 20/10/2014 11:51
a64d9089-3f91-4504-bcad-122bfd0a01e9 20/10/2014 11:50
caedc737-d9dd-4bfb-83fd-400ac5a6af6a 20/10/2014 11:50
1a56651a-d096-45a5-9afa-e6c0c822d892 20/10/2014 11:38
71f07b05-8310-4f1d-b5e9-70a514e8a43e 20/10/2014 11:38
2de8971d-d1cf-4077-bac0-be405dd76ff5 20/10/2014 11:38
9ffe41cc-844b-4b93-b172-28154eabfc0c 20/10/2014 11:38
bf95a7d3-0e08-485d-84e9-3638a749244b 20/10/2014 11:38
061112b6-e919-4e87-a815-6c137a48d375 20/10/2014 11:38
1d8ebe85-a5a3-4120-920a-0556be7524c8 20/10/2014 11:38
b0fcb220-1515-4c94-8d35-c65c4cb7743c 20/10/2014 11:38
07430c7b-2424-4f90-8a0d-fb90d3c829f3 20/10/2014 11:38
99b8b695-995f-4bce-a879-8bd0e89cd296 20/10/2014 11:26
d01187a9-bb0a-4bc8-b6fe-9669b5a2d858 20/10/2014 11:26
9b650499-6ac1-42c8-9a92-f762d61deafd 20/10/2014 11:26
ec6044dd-8940-4f6e-8e97-94c23213a973 20/10/2014 11:26
a08bb60e-f686-4417-b5ce-3e736c9ed625 20/10/2014 01:15
4eb90c2b-f9ed-4952-b8e9-71fffe7ecf64 20/10/2014 01:14
03642f9d-09ea-46ea-b66d-62dee98a20fe 20/10/2014 01:14
4cd20689-ad73-4371-88c6-d80f4ed95313 20/10/2014 01:13
c72ee7ad-389a-4a14-a5cf-539765e707c4 19/10/2014 21:08
8593221b-8024-45c0-a07b-85dcf5bc9035 19/10/2014 21:07
32a5c4d7-dad9-4fc2-b31e-716881e4cefe 19/10/2014 21:07
d46d8d27-f26e-488c-ab89-5f029d139246 19/10/2014 21:07
da22093e-970d-4724-b074-2ae494745e0b 19/10/2014 20:46
3ca99f2a-0138-4403-81fa-e4245ff9a7db 19/10/2014 20:45
c7252857-d6bb-4c0d-95e5-83f1fd9bf175 19/10/2014 20:45
87c7b0a9-a2b5-4c98-9953-cf684c15f3d5 19/10/2014 20:44
c60f13f8-18b5-42b6-9b02-810cb5a77347 19/10/2014 20:44
188ba801-1616-4048-a941-b60126788efe 19/10/2014 20:44
1c3d4f1e-c3be-469a-a348-5e93d1443bae 19/10/2014 20:44
852bf33f-d3b2-40d3-820e-aea7e1c367da 19/10/2014 20:20
d5cda65a-4fa7-4f9e-b5a0-bacfb1bfcebd 19/10/2014 20:20
d6b7137a-d347-4a39-91a6-e0e5f817b71b 19/10/2014 20:20
a031b2f8-cbb0-4fd5-abf1-a557a4021ce7 19/10/2014 20:20
58cf92b6-f4d7-4ab8-98ea-89cc311338df 19/10/2014 20:20
The crashes are intrusive but Firefox itself is not usually affected - so isolating the plugins works as intended.
(I tried creating a separate thread for this but the process stalled at Stage 3)

Plugin-container bug report

Similar Messages

Maybe you are looking for