Plugin Container and Firefox Continuously Crash
Hello, so basically, throughout the day, firefox will crash. Sometimes it will just straight up crash itself and leave nothing but the, "We're sorry, firefox has crashed" screen. I do send off the crash report most of the time, but it's gotten to the point where I've gotten really tired of it, and will search for help. Most of the time, the "Plugin Container for Firefox" will crash with it.
I have tried during hardware acceleration off. It does not help with the crashing, and seems to only expedite how fast firefox crashes from that issue.
Crash Reports: bp-96b3aa28-c9ee-450b-8e40-105822150618 6/18/2015 5:56 PM bp-3c171ee4-27a7-4443-a3b8-af0ad2150617 6/16/2015 11:36 PM bp-3cee10e8-1fca-4612-b7d7-af56a2150615 6/15/2015 12:06 AM bp-814a81c9-7041-4a93-b59e-407272150615 6/14/2015 11:44 PM bp-59bda2a7-536b-4b57-bd50-74d902150613 6/13/2015 11:43 AM
All Replies (6)
You can check for problems with current Shockwave Flash plugin versions and try this:
- make sure you have the latest Flash version:
http://www.adobe.com/special/products/flashplayer/fp_distribution3.html - check for updates for your graphics drive drivers
https://support.mozilla.org/kb/upgrade-graphics-drivers-use-hardware-acceleration - disable protected mode in the Flash plugin (Flash 11.3+ on Windows Vista and later)
- disable hardware acceleration in the Flash plugin
See:
This is something of a random assortment of crash reports.
Three are OOM, or out-of-memory, problems. Firefox halts when it requests a chunk of memory to perform the next operation and Windows says it isn't available. Total Windows memory usage was recorded as being under 40% at the time, so this seems unusual. But on the other hand, the detection of total "physical" system memory seems to be erroneous, over 30GB, which seems way to large. I don't know how to interpret that.
One report is a shutdown crash. Since you have the Norton Toolbar extension, try not to shut down using the "red X" but always use the menu to Exit.
The fifth report doesn't ring a bell.
@cor-el I am trying out your fixes right now, albeit some were already in place. I'll let you know how they go.
@jscher2000 It's not incorrect, I run 32GB or RAM. And roger, I'll start using the menu exit. That's kind of silly that Norton would cause you to have to use Exit instead of the normal red X. So it's just a whole bunch of things compounding then, huh?
32GB, wow. Since Firefox can only use about 3GB of RAM, maybe it really is running out of 32-bit address space? Usually when memory use gets high, Firefox becomes increasingly sluggish. I don't know whether you've noticed that. You could use the Windows 7 Resource Monitor to keep an eye on Firefox from time to time.
@jscher2000 Yeah, it usually starts getting noticeably sluggish around 2GB worth (on the 1.9 end) and ends up eventually crashing right there. Maybe I should close some tabs...
At that point, you also could try the three buttons in the "Free memory" section of the internal about:memory page. That may knock off a few hundred megabytes.
As with other about: pages, you can type or paste that into the address bar and press Enter to load it. You also can bookmark it to save time with typing in the future.