Firefox crashes daily in plugin container on Facebook
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
선택된 해결법
Yes noted thanks. We are not yet certain of course if this will remain the case when Firefox 50 makes it through to Release.
문맥에 따라 이 답변을 읽어주세요 👍 0모든 댓글 (20)
¡Hola Bob!
As far as I know Facebook does not need Java to function.
We really appreciate you sticking around and helping us get to the bottom of this.
Your last crash seems to be new and also affecting others so I've filed https://bugzilla.mozilla.org/show_bug.cgi?id=1291294 for it to be investigated.
Could you please copy and paste the contents of about:support from the 32-bit Firefox that crashes the most?
Could you please tell us with as much precission as you can what exactly you're doing on facebook.com that leads to the crash? watching videos in sequence? Scrolling infinitely to the bottom? Other?
¡Gracias!
OK, turned off the theme and all plugins. Crashed at 2.886 GB RAM usage.
bp-74e05269-9fdb-45b8-a4a8-be1952160802
You were right. Did not need Java.
See what this has to say. Right back. And I also appreciate you hanging with me. So frustrating.
~Bob
Application Basics
Name: Firefox Version: 47.0.1 Build ID: 20160623154057 Update Channel: release User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:47.0) Gecko/20100101 Firefox/47.0 OS: Windows_NT 6.1 x86 Multiprocess Windows: 0/1 (Disabled) Safe Mode: false
Crash Reports for the Last 3 Days
Report ID: bp-74e05269-9fdb-45b8-a4a8-be1952160802 Submitted: 5 minutes ago
Report ID: bp-b73518c5-b313-4a27-9224-c8c272160802 Submitted: 2 hours ago
All Crash Reports
Extensions
Name: Addon List Dumper (restartless) Version: 0.2.1-signed.1-signed Enabled: true ID: addonListDumper@jetpack
Name: All-in-One Sidebar Version: 0.7.28 Enabled: true ID: {097d3191-e6fa-4728-9826-b533d755359d}
Name: Autofill Forms Version: 1.1.4 Enabled: true ID: autofillForms@blueimp.net
Name: Bookmarks Checker - check for bad links Version: 5.8.1 Enabled: true ID: firefoxbookmarkchecker@everhelper.me
Name: Classic Theme Restorer Version: 1.5.5.1 Enabled: true ID: ClassicThemeRestorer@ArisT2Noia4dev
Name: Classic Toolbar Buttons Version: 1.5.2.1 Enabled: true ID: CSTBB@NArisT2_Noia4dev
Name: Close Button Version: 0.4.1.1-signed.1-signed Enabled: true ID: {962e0d4d-6b89-4b73-aa72-df03360da12e}
Name: Color Management Version: 0.5.3.1-signed.1-signed Enabled: true ID: color_management@seanhayes.name
Name: Cookie Manager Button Version: 1.0.1.6.1-signed.1-signed Enabled: true ID: {4568ed01-8341-4961-b3d5-98ab068ce4c0}
Name: Disconnect Version: 3.15.3.1-signed.1-signed Enabled: true ID: 2.0@disconnect.me
Name: Download YouTube Videos as MP4 Version: 1.8.7 Enabled: true ID: {b9bfaf1c-a63f-47cd-8b9a-29526ced9060}
Name: Exif Viewer Version: 2.00.1-signed.1-signed Enabled: true ID: exif_viewer@mozilla.doslash.org
Name: Extended Statusbar Version: 2.0.5 Enabled: true ID: {daf44bf7-a45e-4450-979c-91cf07434c3d}
Name: Extension List Dumper 2 Version: 1.0.1 Enabled: true ID: extension_list_dumper_2@iceberg.it
Name: Favicon Restorer Version: 1.4.1-signed.1-signed Enabled: true ID: faviconrestorer@masserog.it
Name: fireform Version: 0.7.5.1-signed.1-signed Enabled: true ID: fireform@mozilla.org
Name: Firefox Hello Version: 1.3.2 Enabled: true ID: loop@mozilla.org
Name: Forecastfox (fix version) Version: 2.4.4 Enabled: true ID: forecastfox@s3_fix_version
Name: FxIF Version: 0.4.9.1 Enabled: true ID: {11483926-db67-4190-91b1-ef20fcec5f33}
Name: Google Similar Images Version: 0.5.1-signed.1-signed Enabled: true ID: nishan.naseer.googimagesearch@gmail.com
Name: Google Translator for Firefox Version: 2.1.0.5.1.1-signed Enabled: true ID: translator@zoli.bod
Name: gui:config Version: 1.10.1 Enabled: true ID: guiconfig@slosd.net
Name: Integrated Google Calendar Version: 1.5.1 Enabled: true ID: intgcal@egarracingteam.com.ar
Name: MeasureIt Version: 0.4.15 Enabled: true ID: {75CEEE46-9B64-46f8-94BF-54012DE155F0}
Name: Multi-process staged rollout Version: 1.0 Enabled: true ID: e10srollout@mozilla.org
Name: Open in Wayback Machine Version: 2.0.2 Enabled: true ID: jid1-D3J3CDl5LFaX5A@jetpack
Name: Organize Status Bar (Revived) Version: 0.1.0.1-signed.1-signed Enabled: true ID: obsrev@alexancarlproject.net
Name: Places Maintenance Version: 2.0.1 Enabled: true ID: places-maintenance@bonardo.net
Name: Pocket Version: 1.0.2 Enabled: true ID: firefox@getpocket.com
Name: Precise Clear History Version: 1.3.1-signed.1-signed Enabled: true ID: preciseclearhistory@vano
Name: QuickDrag Version: 2.1.3.23.1-signed.1-signed Enabled: true ID: quickdrag@mozilla.ktechcomputing.com
Name: Replace Bookmark Version: 1.6.1 Enabled: true ID: bmreplace@dgutov.github.com
Name: selectivecookiedelete Version: 4.1.1-signed.1-signed Enabled: true ID: selectivecookiedelete@siju.mathew
Name: Session Manager Version: 0.8.1.12 Enabled: true ID: {1280606b-2510-4fe0-97ef-9b5a22eafe30}
Name: Shortcuts for Google™ Products Version: 1.1.6 Enabled: true ID: jid1-SVJwkBGCTt4PyQ@jetpack
Name: Show Host IP Version: 0.1.3.1-signed.1-signed Enabled: true ID: gethostip@lissak.fr
Name: Status-4-Evar Version: 2015.11.16.23.1-signed.1-let-fixed Enabled: true ID: status4evar@caligonstudios.com
Name: Stylish Version: 2.0.6 Enabled: true ID: {46551EC9-40F0-4e47-8E18-8E5CF550CFB8}
Name: SwiftTabs Version: 0.4.1.0.1-signed Enabled: true ID: {5F4EC95A-FFA8-11DE-898C-667D55D89593}
Name: Tab Counter Version: 1.9.9.3 Enabled: true ID: tabcounter@morac
Name: Tab Mix Plus Version: 0.5.0.0 Enabled: true ID: {dc572301-7619-498c-a57d-39143191b318}
Name: TinEye Reverse Image Search Version: 1.2.1 Enabled: true ID: tineye@ideeinc.com
Name: TinyURL Generator Version: 2.6.1.1-signed.1-signed Enabled: true ID: tinyurl.addon@fast-chat.co.uk
Name: Toolbar Buttons Version: 1.1.1-signed.1-signed Enabled: true ID: {03B08592-E5B4-45ff-A0BE-C1D975458688}
Name: checkCompatibility Version: 1.3.1-signed.1-signed Enabled: false ID: check-compatibility@dactyl.googlecode.com
Name: Expire history by days Version: 1.2.0 Enabled: false ID: expire-history-by-days@bonardo.net
Name: FatWallet Express Version: 6.4.0.0 Enabled: false ID: addon@fatwallet.com
Graphics
Adapter Description: NVIDIA Quadro K1000M Adapter Description (GPU #2): Intel(R) HD Graphics 4000 Adapter Drivers: nvd3dumx,nvwgf2umx,nvwgf2umx nvd3dum,nvwgf2um,nvwgf2um Adapter Drivers (GPU #2): igdumd64 igd10umd64 igd10umd64 igdumd32 igd10umd32 igd10umd32 Adapter RAM: 2048 Adapter RAM (GPU #2): Unknown Asynchronous Pan/Zoom: none ClearType Parameters: Gamma: 2200 Pixel Structure: R ClearType Level: 100 Enhanced Contrast: 300 Device ID: 0x0ffc Device ID (GPU #2): 0x0166 DirectWrite Enabled: false (6.2.9200.17568) Driver Date: 11-5-2015 Driver Date (GPU #2): 8-21-2012 Driver Version: 10.18.13.5445 Driver Version (GPU #2): 9.17.10.2843 GPU #2 Active: false GPU Accelerated Windows: 0/1 Basic (OMTC) Subsys ID: 21f517aa Subsys ID (GPU #2): 21f517aa Supports Hardware H264 Decoding: No; Hardware video decoding disabled or blacklisted Vendor ID: 0x10de Vendor ID (GPU #2): 0x8086 WebGL Renderer: Google Inc. -- ANGLE (NVIDIA Quadro K1000M Direct3D9Ex vs_3_0 ps_3_0) windowLayerManagerRemote: true AzureCanvasAccelerated: 0 AzureCanvasBackend: skia AzureContentBackend: cairo AzureFallbackCanvasBackend: cairo
Important Modified Preferences
accessibility.lastLoadDate: 1466643421 accessibility.typeaheadfind.flashBar: 0 browser.cache.disk.capacity: 358400 browser.cache.disk.filesystem_reported: 1 browser.cache.disk.hashstats_reported: 1 browser.cache.disk.smart_size_cached_value: 1048576 browser.cache.disk.smart_size.first_run: false browser.cache.frecency_experiment: 3 browser.download.folderList: 0 browser.download.importedFromSqlite: true browser.download.manager.showWhenStarting: false browser.places.smartBookmarksVersion: 7 browser.search.openintab: true browser.search.useDBForOrder: true browser.sessionstore.max_tabs_undo: 12 browser.sessionstore.restore_on_demand: false browser.sessionstore.upgradeBackup.latestBuildID: 20160623154057 browser.startup.homepage: http://my.msn.com/ browser.startup.homepage_override.buildID: 20160623154057 browser.startup.homepage_override.mstone: 47.0.1 browser.tabs.closeWindowWithLastTab: false browser.tabs.drawInTitlebar: false browser.tabs.insertRelatedAfterCurrent: false browser.tabs.loadInBackground: false browser.tabs.onTop: false browser.tabs.remote.disabled-for-a11y: true browser.tabs.selectOwnerOnClose: false browser.tabs.tabMaxWidth: 135 browser.tabs.tabMinWidth: 85 browser.tabs.warnOnClose: false browser.tabs.warnOnOpen: false dom.apps.reset-permissions: true dom.ipc.plugins.enabled: false dom.ipc.plugins.flash.disable-protected-mode: true dom.max_script_run_time: 20 dom.mozApps.used: true dom.w3c_touch_events.expose: false extensions.checkCompatibility.33.0: false extensions.checkCompatibility.36.0: false extensions.checkCompatibility.37.0: false extensions.checkCompatibility.38.0: false extensions.checkCompatibility.39.0: false extensions.checkCompatibility.40.0: false extensions.checkCompatibility.41.0: false extensions.checkCompatibility.42.0: false extensions.checkCompatibility.43.0: false extensions.checkCompatibility.44.0: true extensions.checkCompatibility.nightly: true extensions.lastAppVersion: 47.0.1 font.default.x-western: sans-serif font.internaluseonly.changed: true font.language.group: x-western font.name.monospace.x-western: Lucida Console font.name.sans-serif.x-user-def: Arial font.name.serif.x-western: Arial font.size.variable.x-user-def: 16 general.autoScroll: false
More. It ran over 10K characters. And I deleted the older crashes and NONE of the add-ins were running last two crashes.
gfx.color_management.display_profile: C:\Windows\System32\spool\drivers\color\DELL-U2410.icm gfx.color_management.mode: 1 gfx.crash-guard.d3d11layers.appVersion: 47.0 gfx.crash-guard.d3d11layers.deviceID: 0x0ffc gfx.crash-guard.d3d11layers.driverVersion: 10.18.13.5445 gfx.crash-guard.d3d11layers.feature-d2d: true gfx.crash-guard.d3d11layers.feature-d3d11: true gfx.crash-guard.glcontext.appVersion: 45.0.2 gfx.crash-guard.glcontext.deviceID: 0x0ffc gfx.crash-guard.glcontext.driverVersion: 8.17.12.9688 gfx.crash-guard.glcontext.gfx.driver-init.direct3d11-angle: true gfx.crash-guard.glcontext.gfx.driver-init.webgl-angle: true gfx.crash-guard.glcontext.gfx.driver-init.webgl-angle-force-d3d11: false gfx.crash-guard.glcontext.gfx.driver-init.webgl-angle-force-warp: false gfx.crash-guard.glcontext.gfx.driver-init.webgl-angle-try-d3d11: true gfx.crash-guard.status.d3d11layers: 2 gfx.crash-guard.status.d3d9video: 2 gfx.crash-guard.status.glcontext: 2 gfx.direct2d.disabled: true gfx.direct3d.last_used_feature_level_idx: 0 gfx.direct3d.prefer_10_1: true gfx.driver-init.appVersion: 42.0 gfx.driver-init.deviceID: 0x0ffc gfx.driver-init.driverVersion: 9.18.13.3302 gfx.driver-init.feature-d2d: true gfx.driver-init.feature-d3d11: true gfx.driver-init.status: 2 javascript.options.strict: true layers.acceleration.disabled: true media.gmp-eme-adobe.abi: x86-msvc-x64 media.gmp-eme-adobe.autoupdate: true media.gmp-eme-adobe.lastUpdate
~Bob
OK, to crash Facebook. Go to news feed, most recent and scroll. You can watch the memory of Firefox get eaten as you scroll (or page down) in task manager. It is that simple. Occasionally, I watch an embedded video.
Have a lot of friends? Not been on for a day or so and want to catch up? Likely will crash before you complete the check of new items since the last visit.
In 32 bit FF on 64bit Win 7 OS, one table can start with 100-2-oo MB or RAM used. Will crash between 2.8 and 2.9 GB repeatedly as you can see from the last two.
~Bob
¡Hola Bob!
Whoa! 40+ add-ons, that's quite the collection =)
Can you make it crash a few times while in "Safe Mode"?
Please see Diagnose Firefox issues using Troubleshoot Mode.
¡Gracias!
Both of the last crashes were in safe mode, Alex.
~Bob
Thanks! That's an useful data point then.
Please see Profile Manager - Create, remove or switch Firefox profiles.
Try creating a new profile and make it crash.
Another data point is that I do not see this crash signatures appearing on 49, so perhaps using Developer Edition might make these go away.
Would you be willing to give that a go?
¡Gracias! Alex
I will try a profile.
I just read that 48 disallows unsigned add-ons? If so, that concerns me. No idea how that will affect me. If it does not, then would try 49. But if it does, may not. Will need a pointer. One thing at a time :)
Alex Thanks for filing the bug Alex, but it may be rather optimistic as the signature does not seem to even make it in to the top 300. Obviously if would help if we had STR and others who are able to reproduce it.
I am sure you would have said if you had seen any behaviour like this yourself with Firefox crashing daily on Facebook. (I do not use Facebook myself)
Bob, Looks like that crash was within about 20 minutes. If you did that with one tab open and get an OOM crash it is pretty serious. The good point however is it may be relatively quick and easy to reproduce.
I did note the crashing computer had not crashed for a couple of week, I guess that is just because you have not used it for a week, or are things improving slightly ?
Would you mind trying another couple of times with that crashing computer in that configuration and see if we can get another couple of Crash IDs. It would be interesting to see if thy are they same crash signatures or if they vary.
Your Machines or Firefox ?
I can understand why you consider it to be a Firefox problem, and part or all of it may indeed be a Firefox problem, but there must be something somehow special about your computers that makes you see this and not others.
Obviously if others saw things similar to what happens on your three computers Firefox/Mozilla would be well aware of the problem. We would pick it up internally on: The Forum, Feedback comments, Crash Reports/Stats & Telemetry. Externally websites including Facebook would be awash with comments.
And I will guarantee I could make this happen on a fresh install out of the box. Its not Windows. Nor is it Malware. This is a not a "format the hard drive and reinstall windows" kind of fix. This is an issue with Firefox.
That sounds convincing, but if I try on three of my machines all different and all different Operating Systems I can not make it crash. or leak memory like you do.
. Google and you will easily find I am not the only one with issues. And FF memory leaks have been reported forever.
Firefox is not perfect. Look at the crashes by frequency, and yes the most frequent reasons for crashes are memory related issues. I very much doubt many people see Firefox crashing like you do. The problem with Googling is the self selection bias. With something like 1/2 a billion users if only 1% have a memory crash problem that is millions of users at any one time with such problem. It is not surprising if you Google it you will confirm there are problems seen. What you do not see is the 99 times as many people without such a problem. The Silent Majority They tend not to post to say Firefox is working fine with no memory problems.
I am not saying this to try to dispute your opinion, other than to ask you to "Please try to keep an open mind about possible causes." That also explains why this issue has not already been fixed, not many others are seeing it. I know you will consider me biased Perhaps if you know someone else with a computer with Firefox on it you could ask them how well it works on Facebook, or try a computer in a Library or an internet cafe.
Potentially file a memory leak bug ?
I will try ONE computer. Easiest is a 64 bit machine using 32 bit Firefox. Will crash as memory hits around 3.2 GB. 64 bit has not crashed yet, but as you have seen will use up to 7 GB and NEVER release that memory.
I will wait tillI see your reply to Alex's question about what you did to cause this crash. If crashes are in the configuration I suggested and with only Facebook open that may be sufficient to be able to file a bug about your own problem specifically.
You would need to use about:memory to record the details. That leads to another couple of questions
- Is about:memory showing similar memory figures to what you are mentioning ?
- Does the button on about:memory release the memory ?
I have not really given proper details yet and this post is long enough, however if you have not already seen these could you look at them when you get the spare time please
John,
Not sure you are reading this. Too much to reply to, but I said I deleted all the older crash reports. Only kept today's. Starting fresh since you are starting to believe it is a Firefox issue. So I can crash every session if I push it. I have earned to control. How many crashes reach your metric of a problem?
And just try this:
https://www.google.com/search?q=firefox+crashes+on+facebook+pages&ie=utf-8&oe=utf-8
I can repeatedly crash this in much less than 20 minutes. Repeatedly.
Nothing different on my computers. They are all different. Three operating systems. Similarity is Firefox 32 bit. This is Firefox. Why would Edge not do this? Chrome?
How far did you scroll on Facebook (which you say you do not use) to see if you could make it crash, John? How do you have a news feed if you do not use Facebook?
BTW, I have been online and computing and Beta testing since 1986. 1986. Well familiar with silent majorities. And also how to Google to see if others have issues. See above.
I answered SEVERAL times on what I do to cause the crash. Again, are you reading this?
ONLY Facebook open, safe mode, no theme, no plugins.I have said that.
Look, I am happy to try and help and test. But long emails like this asking me to repeat myself take time away from work I do not have.
Try it yourselves. Open Facebook, news feed, most recent. Page down and watch Task Manager show Firefox eating memory. Go a couple of hundred screens down. Not unusual if you have a lots of friends and been away 24 hours. And using 32 bit Firefox. How much memory do you use? Did you crash?
Sorry. Just feels like you are not reading this John.
~Bob
BTW, John. You saw my screenshots of Firefox 64 using 7 GB of RAM, yes? Normal?
Does that help you agree you have a memory leak? Perhaps you need to keep an open mind as well.
~Bob
in4m8n said
I will try a profile. I just read that 48 disallows unsigned add-ons? If so, that concerns me. No idea how that will affect me. If it does not, then would try 49. But if it does, may not. Will need a pointer. One thing at a time :)
I suggest you have a go with Firefox Developer Edition. I think at least initially Alex is suggesting this as a troubleshooting step rather than anything permanent. A great fact about Firefox DE is that it installs by default as a separate additional browser and with its own profile.
- Download from https://www.mozilla.org/firefox/developer/
- background info https://developer.mozilla.org/Firefox/Developer_Edition
Short answer no
Sorry Bob, but not convinced. I am not sure that proves Firefox has a general memory leak problem as described by you. It only shows you have such a problem with Firefox.
in4m8n said
BTW, John. You saw my screenshots of Firefox 64 using 7 GB of RAM, yes? Normal? Does that help you agree you have a memory leak? Perhaps you need to keep an open mind as well. ~Bob
I know you have memory problems when using Firefox on your three or more machines.. All I am trying to say is most other people doing apparently identical things with Firefox probably do not. No idea why, but it does suggest there is something special or different about your setup and that most other people see or use.
Alex,
Brand new profile. Crashed about 2.5GB use (even a bit lower than usual). One tab open - Facebook of course.
bp-0d997f2d-5813-4c6f-8245-84d062160802
~Bob
John99 said
in4m8n saidI will try a profile. I just read that 48 disallows unsigned add-ons? If so, that concerns me. No idea how that will affect me. If it does not, then would try 49. But if it does, may not. Will need a pointer. One thing at a time :)I suggest you have a go with Firefox Developer Edition. I think at least initially Alex is suggesting this as a troubleshooting step rather than anything permanent. A great fact about Firefox DE is that it installs by default as a separate additional browser and with its own profile.
- Download from https://www.mozilla.org/firefox/developer/
- background info https://developer.mozilla.org/Firefox/Developer_Edition
OK, I will try that. But do tell me, will any of my legacy add-ons have issues if I try 48? Would be good to know.
This one I can test tonight. Easy to remove without affecting my 32 and 64 bit installs and existing profile John?
~Bob
John99 said
Short answer no Sorry Bob, but not convinced. I am not sure that proves Firefox has a general memory leak problem as described by you. It only shows you have such a problem with Firefox. in4m8n saidBTW, John. You saw my screenshots of Firefox 64 using 7 GB of RAM, yes? Normal? Does that help you agree you have a memory leak? Perhaps you need to keep an open mind as well. ~BobI know you have memory problems when using Firefox on your three or more machines.. All I am trying to say is most other people doing apparently identical things with Firefox probably do not. No idea why, but it does suggest there is something special or different about your setup and that most other people see or use.
Have you tested as I detailed on Facebook? Would be so interesting to see.
And sorry John, but I think you are too close to see the issue. Anything using 7GB of ram, especially when a similar browser on the same machine does not come close, must have an issue. As you might have read above, a brand new profile just crashed earlier.
Until you can test Facebook as I detailed and tell me it does not crash and the memory used does not approach 2.5-2.8 GB, I will not believe this is unique to my computers.
~Bob
Different computer. Tested and crashed at less than 1.5 GB memory used by FF:
bp-63761701-ee19-4f98-8a39-5238c2160802
~Bob
Off to try 49
OK, 49 runs plugin container even with Flash disabled. If I could stop that, I could test. But plugin container bloats insteasd of FF and Facebook does not crash "visibly" but stops working. Says there were two unsubmitted crash reports even though I had not crashed. I clicked submit.
So, If I can kill plugin container, I might be able to test this.
Got a trick for that Alex?
~Bob
bp-5e0c3b0c-a688-47f3-9b39-359752160802
bp-29694a5e-c88d-4744-ad36-14acc2160802