Just found a button to clear memory from Ram back. Will try it. But then, would not know when to do this if I was not monitoring Task Manager.

Not particularly useful.

OK, does nothing in 64 bit and only drops 100-200,000 K in Memory Usage in Task Manager. SO no idea when to push and just postpones the crash.

Firemin is a better program, but unfortunately does not help this issue.

~Bob

Still awaiting replies to my and Alex's last comments in the Bug report, but it is often a few days before people get time to respond.

One reply received saying the 32bit report looks fairly normal but the 64bit report looks suspicious. Full comment see link #c12

Looks like we may be hoping for a further comment from another Developer (Mike Hommey - aka glandium).

Meanwhile as you will still be having crashes on 32bit Firefox can you try crashing it again and taking about:memory anonymised reports as you go along. No problem that you do not get the about memory immediately before the crash just get it as near as you can by making reports at suitable intervals. I think ir could be useful to have a crash signature and matching about:memory reported, something we do not have yet.

Additionally it may well be worth trying in Windows Safe mode as well as the other test criteria. i.e. Firefox Safe Mode, all plugins disabled and a relatively new or new profile - so the Developer Edition will have a newish profile that presumably you wil not have modified..

Reports as top level text. I attached a text copy of the top levels of two of the reports you sent me. That appears to have been suitable for the purposes of looking in to your problem, and had no danger of disclosing confidential information, because unlike the big, full zipped reports there is no possibility of anyone being able to drill down and see your Facebook contacts. What I actually posted publicly is here attachment 8778707

Hi John.

1. All addons were off. Safe mode. So whoever said "addon leak" was not paying attention :) Or not properly informed.

2. Will try to do 32 bit about:memory and crash report. Maybe tonight.

3. Always doing this in FF Safe Mode. Always. Will not try Windows Safe Mode for numerous reasons. This is not a Windows issue on three computers, three OS's and three video cards.

4. Already tried new profile and same issues.

5. If Facebook issue, then Edge should have the same problem, no? Life is too short to try Chrome, etc.

Thanks for anonymizing.

More later.

~Bob

in4m8n said

Hi John. 1. All addons were off. Safe mode. So whoever said "addon leak" was not paying attention :) Or not properly informed.

2. Will try to do 32 bit about:memory and crash report. Maybe tonight.

3. Always doing this in FF Safe Mode. Always. Will not try Windows Safe Mode for numerous reasons. This is not a Windows issue on three computers, three OS's and three video cards.

Well it is not looking much like a classic memory leak from Firefox. The matched about:memory and crash report may help shed light on this.

I fail to undersatand why you are so against using Windows own Safe Mode.

• It is something that is very easy to do.
• It is something that is temporary and will add only a couple of minutes to your testing time.
• It may help rule out some possibilities.

I realise you have seen a similar issue on multiple OS versions and multiple machines but you need to remember, amongst other comments

• Honestly, if they are OOMing just on Facebook, odds are they have some addon that is leaking, or they have some graphics driver issue. Lots of people leave Facebook open all the time without problems, so the question is what is unique for this user. about:memory should tell us whether it is addons or graphics drivers. {#c8)
• 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. {myself #answer-902785

4. Already tried new profile and same issues

5. If Facebook issue, then Edge should have the same problem, no? Life is too short to try Chrome, etc.

It is often the case that a problem with a Website having a fault will be seen on differing alternative browsers. However that is not always the case. Whatever you see is some sort of edge case it is apparently not affecting many others.

Have you been able yo reproduce on a Friend | colleague |relatives|internet cafe | machine ? I don't suppose we have fully ruled out malware for instance. Any malware issue could quite possibly have been spread between all your own machines..

Thanks for anonymizing. More later. ~Bob

Looking forward to your next posts, Thanks John

Crashed at about 2.9 GB mem used.

bp-f709a9be-8459-433b-bfe3-d02302160810

Cannot attach thee memory report :( Sent to John.

~Bob

Looking initially at the rather generic OOM signature report

It really would be a good idea to try in Windows own safe mode and get a crash report and about memory report in that basic test configuration.

Meanwhile it may be worth exploring this posibility A supported hotfix is available from Microsoft.

• "Handle leak in the MPEG-2 Video Decoder when you play videos multiple times in Windows Media Player in Windows 7" https://support.microsoft.com/en-us/kb/2704372

  Symptoms
  When you play videos multiple times in Windows Media Player on a computer that is running Windows 7, a handle leak occurs in the Microsoft MPEG-2 Video Decoder. Additionally, the handle count for Windows Media Player increases continuously.
  Cause
  This issue is caused by an error in the MPEG-2 Video Decoder. A handle is created when you play a video, and the MPEG-2 Video Decoder does not release the handle immediately after it is created. Therefore, the handle count increases in proportion to the number of times that you play the video.
  Resolution
  Hotfix information
  Important This hotfix has been re-released to address an issue in which the digital signature on files produced and signed by Microsoft will expire prematurely, as described in Microsoft Security Advisory 2749655. ....

So, Windows Media Player does not run form Facebook. This also happens in Windows 10. Windows 10 has no safe mode. If it were one computer, one operating system, i would try Safe Mode for Windows. It is not and I will not. Hate to jumble up desktop icons, windows sizes, all the things that happen in Safe Mode for NO reason other than your curiosity, John. Just does not make sense.

And if this were a Media Player issue, would happen with other browsers.

So... what have the developers said on my reports?

Thanks.

~Bob

Hi Bob, You have problems on three Windows computers so I see no reason why you do not wish to try Windows Safe Mode.

Can you explain why you are so against it. We do know from the first Firefox 32 about memory reports that Firefox does not look abnormal.

As I already said

 * It is something that is very easy to do.
  * It is something that is temporary and will add only a couple of minutes to your testing time.
  * It may help rule out some possibilities. 

It is not and I will not. Hate to jumble up desktop icons, windows sizes, all the things that happen in Safe Mode for NO reason other than your curiosity, John. Just does not make sense.

I am only asking about doing this as a test. I am not suggesting you need to do that normally. Windows safe mode is not going to make any permanent change to your computer.

Windows 10 has no safe mode

It is a pretty important troubleshooting and testing feature. Microsoft is unlikely to remove it anytime soon, so of course Windows 10 has its own safe mode See this tutorial that explains three methods of starting Windows 10 in Safe Mode.

• Tutorial: Safe Mode - Start Windows 10 in http://www.tenforums.com/tutorials/2304-safe-mode-start-windows-10-a.html

Thanks for Win 10 Safe Mode. Not obvious. F8 of course, no longer works.

But still, I think that is looking for something, anything to blame other than Firefox. I will not be doing safe mode in Windows. The odds of three computers having issues that affect this are minuscule. And send me a computer and I will have that one doing the same in 15 minutes. If I had a 4th, I would try it here as well.

And no one yet seems to acknowledge that using 7 GB of RAM in Win 64 with FF 64 is excessive. 7 GB! Seems to be well swept under the carpet. Not a safe mode issue. Let's let that one go, John.

So, any updates on all the memory and crash reports I have sent?

Thanks.

John99 said

One reply received saying the 32bit report looks fairly normal but the 64bit report looks suspicious. Full comment see link #c12 Looks like we may be hoping for a further comment from another Developer (Mike Hommey - aka glandium). ....

Still hoping for further comment, but it is the 64bit behaviour that looks suspicious, the 32bit probably less so and not sure what is leaking but as I said earlier it possibly does not look like a classic Firefox leak from Facebook.

Any updates? Not only were there no replies n the 64 bit reports, but also 32 with attached crash. Inquiring minds....

Thanks.

~Bob

Could you please do me a summary of what was discussed, what has been resolved and what problem really lack resolve. I'm worried because it has many comments and the conversation is already straining to two months. I await the summary of this topic.

Sure thing:

At least three computers, likely more, with three different Windows operating systems and three different video cards crash 100% consistently Firefox on Facebook, even in Firefox Safe Mode and with only this tab open. Just scroll or page down to see latest posts on the newsfeed and it will crash. Not even a need to view videos as you page.

Memory shown used in Task Manager for Firefox 32 bit shows anywhere from roughly 2.5 - 3.2 GB used when it crashes. 64 Bit FF does not crash, but not unusual to be using 7 GB of memory. I have not tried to get that to increase, but it likely will. It does not crash, but obviously should not be using that kind of memory,

Again, 100% repeatable. Many crash reports sent. Many about:memory reports sent. Seems obvious to me FF is not releasing memory for pages previously viewed. IMHO.

What else would you like me to tell you Samuel?

~Bob

Well, Facebook works with many scripts and most are very large. This can cause a significant consumption of the PC. Possible solutions are below:

1. The constant use open Firefox can cause instability. In this case restart Firefox can work this out.

2. Decer too deep Timeline may require Firefox to use more resources so that all content is displayed. In this case you can open a new tab and close the current.

3. Often the PC is turned on for a long time. In this case, you can restart the PC for the system to release the RAM again.

4. By default, Windows runs many pecessos at startup. You can reduce this by using the msconfig in the Run. Exercise caution when using this tool.

5. Excessive consumption may be caused due to some add-ons. You can disable all go and activating one at a time until you find the possible cause of it.

6. You can restore your Firefox browser that can fix many bugs.

7. A more labor-intensive solution is to create a new Firefox Profile. Just open the Run closed Firefox and type "firefox.exe -p" followed by OK.

Hi Samual, Thanks for your input. Any help and fresh insight is most welcome.

I have certainly not read and remembered all the many comments in this long thread. I am actually surprised it has remained unresolved for so long. I am sure we are missing something. Currently my suspicion is that it is NOT actually all down to Firefox and Windows own SafeMode should be tried. I will add some of my observations. Note also I am; fingers crossed; hoping for further developer comment from the bug Alex filed up- thread.

Samuel Santos said

Well, Facebook works with many scripts and most are very large. This can cause a significant consumption of the PC. Possible solutions are below: 1. The constant use open Firefox can cause instability. In this case restart Firefox can work this out. 2. Decer too deep Timeline may require Firefox to use more resources so that all content is displayed. In this case you can open a new tab and close the current.

Although I have tried to make suggestions so as to understand what is happening I did not specify Bob should restart the computer prior to trying to reproduce this issue.

That is a very valid point. I did however ask for memory reports at intervals, and so we do get to see the initial state.

3. Often the PC is turned on for a long time. In this case, you can restart the PC for the system to release the RAM again. 4. By default, Windows runs many pecessos at startup. You can reduce this by using the msconfig in the Run. Exercise caution when using this tool.

As would be expected Bob was initially reporting memory results as seen by Windows Task manger. That may differ considerably from the about:memory - explicit We are aware Bob is heavily into customising with something like 40 Firefox addons, and I believe Bob is/was a Windows Beta tester.

5. Excessive consumption may be caused due to some add-ons. You can disable all go and activating one at a time until you find the possible cause of it.

We have at least one instance where we have both a Crash ID and a memory report, from a Crash in Safe Mode with no plugins enabled.

6. You can restore your Firefox browser that can fix many bugs. 7. A more labor-intensive solution is to create a new Firefox Profile. Just open the Run closed Firefox and type "firefox.exe -p" followed by OK.

I imagine a clean reinstall may have been tried already. I don't remember for certain without re-reading all the posts, but I do know Bob tried in Developer Edition so that was equivalent to a new clean install and a new profile and was still able to reproduce this issue.

The procedures I mentioned are the ones that would be to solve the problem in question is to create a new profile is the ultimate fix all the problems caused by Firefox. If this does not work, I am afraid that even spending more technical procedures, and is more laborious, would not bring a significant effect for a long preríodo. For this case, the solution would be to report the problem to our developers including contact this topic by using the same link https://input.mozilla.org/pt-BR/feedback problematic product.

Samuel Santos said

Well, Facebook works with many scripts and most are very large. This can cause a significant consumption of the PC. Possible solutions are below: 1. The constant use open Firefox can cause instability. In this case restart Firefox can work this out. 2. Decer too deep Timeline may require Firefox to use more resources so that all content is displayed. In this case you can open a new tab and close the current. 3. Often the PC is turned on for a long time. In this case, you can restart the PC for the system to release the RAM again. 4. By default, Windows runs many pecessos at startup. You can reduce this by using the msconfig in the Run. Exercise caution when using this tool. 5. Excessive consumption may be caused due to some add-ons. You can disable all go and activating one at a time until you find the possible cause of it. 6. You can restore your Firefox browser that can fix many bugs. 7. A more labor-intensive solution is to create a new Firefox Profile. Just open the Run closed Firefox and type "firefox.exe -p" followed by OK.

This is ONLY Firefox using these resources. Not Windows. Restating does nothing. Closing Firefox releases all RAM.

New profile was tried.

Most of these things have been gone through before.

THIS IS A FIREFOX issue. Cut and paste replies ARE NOT OF VALUE. Really. Look at some of the captures of what is using memory. Safe Mode. NO ADDons.

It appears to me that rather than solve the issue the FF developers prefer to try to blame something else other than FF. Perhaps we are all wasting our time? VERY frustrating.

Perhaps another reply below will be more useful I have not yet looked.

~Bob

Thanks for your follow up, John. Indeed you are pretty accurate on your comments and as you mentioned, all of this was tried except for Windows Safe Mode which I believe has no value to this problem. Restating the computer has, of course, been tried.

~Bob