Another three from today.

bp-ba7a7695-810e-45fd-a3ae-ff8c32160706 06/07/2016 15:36 641554e3-b9d0-4b06-8bee-9402b6c3a418 06/07/2016 07:22 8de0e648-1790-4fb2-80bf-d435ce809e58 06/07/2016 07:21

Now more than two weeks since I posted the information requested by @jscher2000 but still no response.

I've had another 6 crashes today, caused by "Plug in container stopped working".

Either Mozilla can help, or they cannot - If not I'll jut have to find another browser, which I DON'T want to have to do!

Some of your crash reports weren’t sent to the Mozilla Servers.

In the address bar, type about:crashes<enter>. Note: If any reports do not have BP in front of the numbers/letters, click it to submit them.

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

Using your mouse, mark the most resent 7 - 10 crash reports, and copy them. Now go to the reply box below and paste them in.

bp-cb6f8054-4ef0-49e5-8034-037b42160705 bp-178560d8-9394-4e23-b3d9-838422160705

Signature: OOM | small

Total Virtual Memory 2,147,352,576 bytes (2 GB) Available Virtual Memory 224,329,728 bytes (213.94 MB) System Memory Use Percentage 96 Available Page File 1,637,646,336 bytes (1.53 GB) Available Physical Memory 68,440,064 bytes (65.27 MB) OOM Allocation Size 1,504 bytes (1.47 KB)

Attention Sumo's there are 35 related bug reports

IPSEng32.dll = Symantec Intrusion Detection

bp-378f2d5d-21e1-45ae-876b-91ba92160630

Signature: RtlLockHeap | HeapLock

Total Virtual Memory 2,147,352,576 bytes (2 GB) Available Virtual Memory 274,862,080 bytes (262.13 MB) System Memory Use Percentage 94 Available Page File 1,450,835,968 bytes (1.35 GB) Available Physical Memory 117,821,440 bytes (112.36 MB)

IPSEng32.dll = Symantec Intrusion Detection

bp-ba7a7695-810e-45fd-a3ae-ff8c32160706

Signature: mozilla::gfx::DrawTargetCairo::InitAlreadyReferenced

Total Virtual Memory 2,147,352,576 bytes (2 GB) Available Virtual Memory 208,769,024 bytes (199.1 MB) System Memory Use Percentage 91 Available Page File 1,411,289,088 bytes (1.31 GB) Available Physical Memory 190,590,976 bytes (181.76 MB)

This is for Sumo's Related Bugs 1283976 ASSIGNED --- Crash in mozilla::gfx::DrawTargetCairo::InitAlreadyReferenced

Please send the other crash reports that were no sent to Mozilla servers.

You are using far too much memory.

Start Firefox in Safe Mode {web Link} by holding down the <Shift>
(Mac=Options) key, and then starting Firefox. A small dialog should appear. Click Start In Safe Mode (not Refresh).

Is the problem still there?

Start your Computer in safe mode with networking. Then start Firefox. Try Safe websites. Is the problem still there?

Starting The Computer In Safe Mode;
Free Online Encyclopedia

https://support.mozilla.org/en-US/kb/websites-look-wrong-or-appear-differently

https://support.mozilla.org/en-US/kb/firefox-slow-how-make-it-faster

https://support.mozilla.org/en-US/kb/firefox-uses-too-many-cpu-resources-how-fix

https://support.mozilla.org/en-US/kb/firefox-hangs-or-not-responding

https://support.mozilla.org/kb/Firefox+is+already+running+but+is+not+responding

Yaaklenmai said

Now more than two weeks since I posted the information requested by @jscher2000 but still no response.

You have no other messages posted here. When did jscher2000 talk to you?

Hi Yaaklenmai, thank you for starting this new thread, I'm not sure how I missed it.

These reports are for crashes that Firefox reported; plugin-container.exe crashes that involve the small Windows crash dialog are not reported to Mozilla. For those, since the most commonly used plugin is Flash, I had suggested trying the steps in this reply as a starting point: https://support.mozilla.org/questions/1119780#answer-869374

Did that help with plugin-container.exe crashes?

As Fred noted, your four most recent crashes show high memory use: 91%, 94%, 95% and 96% memory in use. Firefox doesn't run well under those conditions. On a 2GB system, this may be an ongoing problem.

If this problem is happening on Facebook, I'm not sure there is a workaround because the site's "endless scrolling" design loads more and more content which causes Firefox to use more and more memory...