Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Firefox crashes daily in plugin container on Facebook

  • 193 replies
  • 15 have this problem
  • 2180 views
  • Last reply by John99

more options

OK - I have searched and Googled.

This happens with FF 46 32 bit, 64 bit, portable, on Win 7 32 bit, 64 bit and windows 10. It happen in safe mode. It has all plugins up to date. I t has remove all but needed and non removable add ins - such as Flash, Acrobat Reader, etc. It happens on computers with plenty of RAM (16 GB). Oddly enough, it happens worse with safe mode and plugin container is run-a-way. With normal mode, it appears that plugin container is under control and Firefox itself runs amuck.

So - totally repeatable. Page down in Firefox with one or 50 tabs open - no matter. It will crash. Goes black, or stops responding. Until Firefox closes. NEVER happens with Edge for example.

I have to think it is a Firefox memory leak, but even using Firemin does not help much if at all.

What can be done? I have done my homework!

Problem signature:

 Problem Event Name:	APPCRASH
 Application Name:	plugin-container.exe
 Application Version:	46.0.1.5966
 Application Timestamp:	572818c9
 Fault Module Name:	mozglue.dll
 Fault Module Version:	46.0.1.5966
 Fault Module Timestamp:	572808c3
 Exception Code:	80000003
 Exception Offset:	0000efdc
 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

More info, of course. End of my rope on this one....

Thanks.

~Bob

Chosen solution

Yes noted thanks. We are not yet certain of course if this will remain the case when Firefox 50 makes it through to Release.

Read this answer in context 👍 0

All Replies (20)

more options

¡Hola Bob!

OOM conditions are a fact of life =)

The bug filed would eventually be looked at I'd think.

Do your steps remain being "scroll 200 windows of Facebook news feed"?

If so, I can't reproduce the crash still.

A few differences:

  • I use Debian not Windows
  • I use an ad blocker (uBlock Origin)
  • I use Nightly
  • I use facebook.com for only a few minutes or so a day

¡Gracias! Alex

more options

¡Hola Bob!

A few action items for you:

  • Check your RAM with http://www.memtest.org/#downiso or similars
  • Upgrade your neighboor's Firefox to 64-bit
  • Install Firefox on your relatives' OS X and iOS devices
-)

¡Gracias!

more options

Ola Alex.

Let's see if I can reply a bit.

Windows -could be a huge difference.

Must say that both neighbors computer and the latest Developer build both took longer to crash, but did. FIREFOX just does not release memory using Facebook. The Developers gives back a little, but not much. Enough to forestall the crash for a longer time.

If one has a large number of friends and news feed and only goes to Facebook once a day as I often do, then catching up on the news feed can take several hundred pages of posts. I cannot imagine i am the only one to use Facebook this way. And as mentioned loooong ago, Edge (which has little other redeeming benefits) give back memory of scrolled pages virtually immediately. On the same one of 4 computers that will crash with Firefox.

Alex, this is now 4 different computers. Thsi is not a RAM issue. Not by a long shot. When Firefox 64 can use 7 GB of RAM without releasing using Facebook, it is a FIrefox (or maybe in some odd way that I find inconceivable) an issue with my Facebook account. But it is not RAM. And not malware.

I think it is obvious to me its a Firefox memory issue. And no one seems to want to own that. I have tried, tested, proved, borrowed others computers to show I can do this 100% repeatably. Yet you look for other issues to blame (bad RAM on 4 computers?) And if NOTHING else, I have shown screenshots of FF64 using 5-7 GB of RAM. If you consider that acceptable and customary, what else is there to talk about? I have really tried to get attention to this bug. We keep going in circles.

~Bob

more options

¡Hola Bob!

So I did something I really don't do very often, rebooted into the Win10 partition.

Attached is the memory usage of Nightly after scrolling 300 or so pages of https://www.facebook.com/?sk=nf

Would you be willing to give Nightly a try for a week or so?

¡Gracias! Alex

more options

Presumably that was 64bit Nightly you tried Alex ? (Maybe I missed clues. Presumably you also notice there is an anonymise option on about:memory) Just thought I would ask as I believe

  • Bob does not get crashes with 64 bit Firefox
  • I believe you often use 64 bit Firefox

I note Nicholas Nethercote replied but was not too worried about the result as apparently it was 64bit Firefox.

more options

alex_mayorga said

¡Hola Bob! So I did something I really don't do very often, rebooted into the Win10 partition. Attached is the memory usage of Nightly after scrolling 300 or so pages of https://www.facebook.com/?sk=nf Would you be willing to give Nightly a try for a week or so? ¡Gracias! Alex

That is amazing. That was while Facebook was still an open tab, yes? If so amazing. Cannot guarantee I will use it everyday, but will try it.

~Bob

more options

John99 said

Presumably that was 64bit Nightly you tried Alex ? (Maybe I missed clues. Presumably you also notice there is an anonymise option on about:memory) Just thought I would ask as I believe
  • Bob does not get crashes with 64 bit Firefox
  • I believe you often use 64 bit Firefox
I note Nicholas Nethercote replied but was not too worried about the result as apparently it was 64bit Firefox.

Ahhhh, thanks John. You are correct I have not been able to get FF64 to crash, however I can get it to use 5-7 GB of RAM. I just want to be sure that Facebook was still an open tab that had scrolled 300 pages when that reading was taken. If after the tab was closed that would be expected.

~Bob

more options

Nightly 32 bit uses a minuscule amount of RAM on Facebook. It appears to be clearing RAM and reloading every few scrolls. You can see the progress bar when this happens. It does "burp" each time, taking a few seconds to move to the next page down screen, but will not crash and eat RAM like Wheaties. I am amazed. Somebody listened :)

Would be very nice to improve this so it is more seamless, but what a nice surprise!

When will this get into released builds?

~Bob

more options

It does stutter too much waiting to refresh. Could get annoying. But does not crash. Or use more than 300 some odd MB of RAM on FB.

more options

So, no replies. Does this mean this will be in (and hopefully even polished a bit) in FF50 32 bit and we are done?

~Bob

PS. Thanks to any and everyone that believed me there was an issue and did something to make it better. I am so looking forward...

more options

If nightly works then with any luck it will still work as it moves up from Nightly to Developer Edition then Beta before moving in to Release.

I was hoping to get some other people interested in trying to reproduce the issue. I posted

more options

So the responder asked about Flash. Tuned off as I mentioned many times. Not the issue. Flash disabled. They do realize that memory is not being released. But it seems to (though a tad clunky) in Nightly.Hopefully we can get this done.

more options

Bob do you get crashes both with video autoplay on and video autoplay off ?

(Remember I do not use Facebook, is that still applicable if FlashPlayer is disabled ?)

This is being asked by Andrew has been trying to test this for you.

(/forums/contributors/712188} ... One last thing: are videos set to automatically play for Bob on Facebook? ...
Having autoplay on for videos messes with Firefox's performance and sucks an incredible amount of data. Can you check with the user to see if they have it on before I test it myself? Thanks.
more options

Hi John,

I cannot find a setting for this in Facebook. Please point me to it. But more important, regardless of how it is set Nightly50 does not have this problem!

~Bob

more options

Chosen Solution

Yes noted thanks. We are not yet certain of course if this will remain the case when Firefox 50 makes it through to Release.

more options

Video is on, just downloaded Nightly 52 and with video on works flawlessly.

Looking forward to seeing this in a release.

~Bob

more options

Fx50 is on Developer Edition (nee Aurora) at the moment and should be on the Fx Beta any time soon then the Release in something like six weeks time.

more options

Just read 11/8 for 50. Can only hope this fix makes the cut. It seems to work as should have for a long time in the nightlies I tried. Fingers crossed.

~Bob

more options

Hello. I have been having FF crash for months and nothing I try works. It happens in Safe mode, with and without any plugins or flash etc enabled, no autorun enabled, and with 1 tab open or 20 open. I have updated FF as they come out ans still issue continues. And I have read all the pages here in the thread and stillno changes in crashes. I'm running Wn 7, 16 gb, 64 bit. Let me know if you need more sys info.

Here's the error message:

APPCRASH

 Application Name:	plugin-container.exe
 Application Version:	48.0.0.6051
 Application Timestamp:	5797a45d
 Fault Module Name:	mozglue.dll
 Fault Module Version:	48.0.0.6051
 Fault Module Timestamp:	5797951c
 Exception Code:	80000003
 Exception Offset:	0000f035
 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

Thanks for the help.

more options

We're sorry to hear that Firefox is crashing. In order to assist you better, please follow the steps below to provide us crash IDs to help us learn more about your crash.

The crash report is several pages of data. We need the report numbers to see the whole report.

  1. Enter about:crashes in the Firefox address bar and press Enter. A Submitted Crash Reports list will appear, similar to the one shown below.
  2. Copy the 5 most recent Report IDs that start with bp- and then go back to your forum question and paste those IDs into the "Post a Reply" box.

Note: If a recent Report ID does not start with bp- click on it to submit the report.

(Please don't take a screenshot of your crashes, just copy and paste the IDs. The below image is just an example of what your Firefox screen should look like.)

aboutcrashesFx29

Thank you for your help!

More information and further troubleshooting steps can be found in the Troubleshoot Firefox crashes (closing or quitting unexpectedly) article.

  1. 1
  2. 3
  3. 4
  4. 5
  5. 6
  6. 7
  7. 8
  8. 9
  9. 10