I have just tried to get Firefox Portable to crash but for reasons I don't know it did not crash. It did however, use up almost all my memory that my computer has available, Which is 8Gb of Ram.

This time Firefox Portable went up to 4Mil in memory usage and plug-in container for Firefox was 2Mil. I couldn't get an actual picture of 4Mil memory usage or 2Mil Plug-in container but I can assure that it did reach and go above these numbers.

I also could not get Firefox Portable to crash or have high memory usage on the Mozilla support site.

Here are my latest crashes from normal Firefox.

bp-9e4b1636-4022-4380-a5a5-c7b1f2161001 10/1/2016 7:41 AM bp-7da609e3-8f12-469d-a767-114872161001 10/1/2016 7:45 AM

Signature: nsXPCWrappedJS::nsXPCWrappedJS

inproc_agent.dll = Kaspersky Inproc Agent

shellex.dll = Kaspersky Anti-Virus

Nvwgf2um.dll = NVIDIA Compatible D3D10 Driver = NVIDIA Corporation

This is for Sumo's Related Bugs 1295033 NEW --- Crash in nsXPCWrappedJS::nsXPCWrappedJS

Some of this is speculation rather than evidence based hard facts, but I have now read through the thread, but not tried looking at all the many Crash reports.

TL:DR Even this is fairly long, but trying to summarise my thoughts in bullet points.

1. Use at least on a trial basis (I suggest the Developer Edition 64 bit)
   1. try Fx50 or newer. Fx 50 - it may solve Facebook related crashes.
   2. (You have 8GB and a 64bit OS) so use 64bit Firefox at least with Facebook. Any Fx64bit will probably not crash due to memory issues with Facebook.
   3. You could also try the experimental multi process Firefox
      • It will almost certainly break some addons at present. That is why it is not generally offered to those using add-ons.
      • It is likely to be faster.
      • It is able to crash and restore individual tabs rather than the whole browser having to restart.
2. Bite the bullet and test with Kaspersky temporarily uninstalled

Thanks for trying to stick with Firefox and this thread. Most people would probably just give up and use another browser. When that happens not only do we lose a Firefox user, but we probably miss opportunities to identify and fix issues (or at least find workarounds for the issues) that cause those people to abandon Firefox.

The general situation with Facebook & Out Of Memory issues If someone has Firefox crashes and gets a consistent single Crash Signature that is seen with lots of other people it tends to get fixed quickly as a priority, and the crash signature clearly identifies those affected. With the diversity of platforms and customisations then the code on different websites however it can be very difficult to pin down what causes some issues. Unfortunately then instead of us volunteers being able to suggest potential specific fixes from a short list of probabilities we have to resort more to a process of elimination. That is time consuming and rather unsatisfactory for all concerned. On the up side Firefox's built in tools, the crash reporting & telemetry are improving all the time

I did get involved in the later stages of a long running thread on Facebook crash issues. The Original Poster - Bob, had from the outset determined there were memory issues and that 64 bit Firefox did not crash. I am not a Facebook user, and even borrowing someone else's credentials I could not reproduce the issue. I had just started to get assistance with other contributors in testing this out when Bob discovered the issue was fixed for him in Fx50. It may be instructive for you to see what happens if you tried the Steps To Reproduce [STR] of Bobs problem, does that consistently also cause your Firefox to crash.

• [Resolved in Fx50] Facebook users, ideal problem to look at on Sumo Day
  /forums/support-forum-contributors/712188

Facebook uses a lot of complex scripting and has potential for creating a lot of content including lots of video. There are many add-ons that going to interact with facebook content so that just add-ons to the complications. Facebook is potentially going to use a lot of memory even if it is not leaking memory directly there is probably potential for add-ons or graphics to leak memory.

64 bit Developer Edition A disadvantage of this is that by default it updates continuously and frequently. It is however pretty stable,(I usually use ity as my day to day browser) allows testing of multi-process Firefox (I think it is probably turned on by default now) and it installs by default as a separate browser with a separate Firefox profile. Possibly it would be a good idea to try using that for all facebook use and your ordinary Firefox fro everything else. Does that improve things ?

• https://www.mozilla.org/firefox/channel/#developer

If necessary we can start to look at specific messages you are getting and at details of Firefox memory use, but that's long winded and no guarantee of a success for fixing the overall multiple issues. Firefox should not be crashing and unresponsive.

Crash Reports Your last crash reports, are similar to some previous ones, as can be seen from Fred's comment above.

• _{Your reports
  bp-9e4b1636-4022-4380-a5a5-c7b1f2161001
  bp-7da609e3-8f12-469d-a767-114872161001}
• _{The related bug: Bug 1295033 - Crash in nsXPCWrappedJS::nsXPCWrappedJS}
• My observation - about 50% of those people use Kaspersky software but Kasapersky may not be responsible for a recent spike in that signature (#c12)

Kaspersky I think it is worth testing with this temporarily uninstalled, but for instance whilst over half the people with that crash signature use Kaspersky there does not seem to be an obvious causal link.

• We may be blaming Kaspersky unnecessarily, the red flags in Crash stats are only an indication of lack of debug symbols.
• That lack of debug symbols, and the fact that security software uses binaries and code injection does complicate troubleshooting and diagnosis of problems. That may make it more likely Kaspersky is involved but we find it difficult to detect the problem
• Disabling rather than uninstalling security software does not always work to remove causes of crashes or Firefox failures (as demonstrated in a very recent Fx 49 issue )
• Windows built in / free security software should be sufficient to keep you safe whilst testing without Kaspersky

Alright, I have tried with Firefox 50, and it also crashed. The thing about my crashes that are different from what was in the thread that was posted is that, I don't even have to scroll though facebook, it just keeps climbing and climbing until it crashes.

While facebook does crash, it is not the only site that crashes, I can't even browse some forums without firefox crashing, I.E TomsHardWare.

Here are my latest crashes.

bp-21858090-3936-40eb-a89d-fb4ae2161009 10/8/2016 7:48 PM bp-29dc8a15-3ca2-48d7-87e3-8d0c92161009 10/8/2016 7:47 PM bp-72f30e17-8967-4e86-a50c-a89de2161009 10/8/2016 7:47 PM bp-f4441c0f-2137-464c-a06a-333d32161009 10/8/2016 7:47 PM bp-1137d717-d509-4351-afca-9a2a62161009 10/8/2016 7:47 PM bp-aa0a0f70-1f17-434a-a47c-96ae72161009 10/8/2016 7:47 PM bp-519fcd3f-1aa8-458a-bf79-e9f222161009 10/8/2016 7:47 PM bp-8fd55bdf-90d9-47f5-8649-6d65c2161006 10/6/2016 8:12 AM bp-30383ff1-0cbc-424b-a5f5-18f8a2161005 10/4/2016 9:16 PM

Product Firefox Release Channel aurora Version 51.0a2 Build ID 20161008004004 OS Windows 7 OS Version 6.1.7601 Service Pack 1 ++++++++++++++++++++++++++++++++++++++++++++ bp-21858090-3936-40eb-a89d-fb4ae2161009

Signature: OOM | small

Total Virtual Memory 4,294,836,224 bytes (4 GB)

Available Virtual Memory 310,755,328 bytes (296.36 MB)

Available Page File 6,939,471,872 bytes (6.46 GB)

Available Physical Memory 852,328,448 bytes (812.84 MB)

System Memory Use Percentage 90

Attention Sumo's there are 30 related bug reports

inproc_agent.dll = Kaspersky Inproc Agent

Nvwgf2um.dll = NVIDIA Compatible D3D10 Driver = NVIDIA Corporation

Have you updated Kaspersky? Have you tried disabling Kaspersky?

When you started this question, you were using Firefox 48. Did you have any problem with v47 or v46?

Product Firefox Release Channel release Version 49.0.1 Build ID 20160922113459 OS Windows 7 OS Version 6.1.7601 Service Pack 1

bp-29dc8a15-3ca2-48d7-87e3-8d0c92161009 bp-72f30e17-8967-4e86-a50c-a89de2161009

Signature: F1398665248

Attention Sumo's there are 25 related bug reports

Process Type plugin Shockwave Flash Version: 23.0.0.162

inproc_agent.dll = Kaspersky Inproc Agent +++++++++++++++++++++++++++++++++++++++++ Product Firefox Release Channel release Version 48.0.2 Build ID 20160823121617 OS Windows 7 OS Version 6.1.7601 Service Pack 1

bp-f4441c0f-2137-464c-a06a-333d32161009

Signature: mozalloc_abort | NS_DebugBreak | mozilla::ipc::MessageChannel::OnChannelErrorFromLink

remote_eka_prague_loader.dll = Kaspersky Anti-Virus

inproc_agent.dll = Kaspersky Inproc Agent

This is for Sumo's Related Bugs 1240895 RESOLVED FIXED Twitter crashes the browser

1171307 RESOLVED FIXED [e10s] crash in mozalloc_abort(char const* const) | NS_DebugBreak | mozilla::ipc::MessageChannel::OnChannelErrorFromLink()

FredMcD said

Product Firefox Release Channel aurora Version 51.0a2 Build ID 20161008004004 OS Windows 7 OS Version 6.1.7601 Service Pack 1 ++++++++++++++++++++++++++++++++++++++++++++ bp-21858090-3936-40eb-a89d-fb4ae2161009 Signature: OOM | small Total Virtual Memory 4,294,836,224 bytes (4 GB) Available Virtual Memory 310,755,328 bytes (296.36 MB) Available Page File 6,939,471,872 bytes (6.46 GB) Available Physical Memory 852,328,448 bytes (812.84 MB) System Memory Use Percentage 90 Attention Sumo's there are 30 related bug reports inproc_agent.dll = Kaspersky Inproc Agent Nvwgf2um.dll = NVIDIA Compatible D3D10 Driver = NVIDIA Corporation

---

Have you updated Kaspersky? Have you tried disabling Kaspersky?

When you started this question, you were using Firefox 48. Did you have any problem with v47 or v46?

I have updated Kaspersky as much as I could. But I have not tried to disable Kaspersky, As I don't believe this to be the problem.

In the recent replies I was told to try the developer version to see if it still crashed, It still did. I have not tried V47 or V46, I also don't remember if it crashed or not.

Well judging from the lack of reply from anyone since I made my last reply, I'm going to say that my problem will probably never be fixed, and that support for my problem has been stopped.

I'm just going to say this, I now have a problem where Firefox crashes and leaves a process open in my task manager that clearly says Firefox, it prevents me from exiting out of Firefox. I've tried end process and end process tree, neither of which worked, I ended up having to restart my computer, everything else works fine on my computer. Firefox does not.

I will look for another browser other than Firefox.