Why does the Firefox Plug In Container keep causing crashes?
These are all of the requested Crash Reports that Firefox has logged since the beginning of May.
Submitted Crash Reports Report ID Date Submitted 641554e3-b9d0-4b06-8bee-9402b6c3a418 06/07/2016 07:22 8de0e648-1790-4fb2-80bf-d435ce809e58 06/07/2016 07:21 bp-cb6f8054-4ef0-49e5-8034-037b42160705 05/07/2016 22:08 bp-178560d8-9394-4e23-b3d9-838422160705 05/07/2016 18:38 bp-378f2d5d-21e1-45ae-876b-91ba92160630 30/06/2016 16:20 bp-bb28ad03-ea04-4c68-94f6-0e0a72160628 28/06/2016 18:06 bp-dd5d3943-766d-436f-a0df-18adb2160628 28/06/2016 11:03 bp-adc9dd37-c5f8-4b67-a71d-a05f02160624 24/06/2016 16:09 bp-39a23900-6d6d-4f86-bd7b-d3db72160624 24/06/2016 14:56 bp-2559a4bb-0cfe-4ec6-bbcc-8a5962160624 24/06/2016 13:47 bp-df6814eb-26b8-46a3-9353-39ff92160624 24/06/2016 12:59 bp-454588ea-49d6-4d35-aa92-9f1fc2160623 23/06/2016 12:06 bp-d50047c0-afad-4f9e-aa59-bc34d2160621 21/06/2016 16:37 5d5e4edc-61c8-498a-9a2e-3153207f6bdc 20/06/2016 20:47 bp-ed804638-651f-4735-a1fb-0a5f02160620 20/06/2016 12:48 33c7718b-9556-497b-bc2e-e38f1a368240 19/06/2016 08:03 bp-d5d61a68-db74-4670-a3fa-2636f2160618 18/06/2016 15:16 bp-0c3597f4-0385-4210-913a-f42242160618 18/06/2016 14:42 f6a93055-8d62-40fb-ba53-948272e366bd 17/06/2016 23:23 bp-5e9b1c99-d142-4ad8-9676-078a42160617 17/06/2016 22:57 bp-2c0e6af5-f17d-4845-bf4c-661c22160617 17/06/2016 19:16 bp-4a3e2970-4430-4231-939f-0016a2160617 17/06/2016 13:25 96e8cfe9-f5fc-4273-adcf-4375da4ffa02 16/06/2016 23:15 c19420ae-c155-4d79-919b-0bedaaa23ce0 13/06/2016 20:17 8480df43-9a26-4f65-aba1-cbeb688edfc3 12/06/2016 23:06 d26088f6-2f5e-41dd-8c73-8d9a9589e068 11/06/2016 21:53 7c0c7a8e-b021-4fc0-81d8-f7f9031c5c05 10/06/2016 22:55 bp-341f3983-07c1-4a2b-9702-745e62160610 10/06/2016 10:56 bp-0fafe1bd-a908-41f6-9ade-fed102160609 09/06/2016 13:12 bp-c99bbb63-8e50-4700-8c25-b781b2160608 08/06/2016 16:54 8bd187c4-6e89-4e6f-b51d-9fb0b672f970 06/06/2016 21:04 bp-be548669-2414-445d-9a0b-e5ed72160605 05/06/2016 14:21 8974cc3e-dc26-4fd9-84ee-a95c2545398a 04/06/2016 22:58 bc3a2c54-e590-400f-bcd5-6aafe2669958 03/06/2016 23:28 bp-5ba6ab1e-3a8c-4cf9-9b16-ab7d52160602 02/06/2016 19:11 bp-ca7a5c85-c0d9-41a3-81de-0f8462160602 02/06/2016 15:54 bp-ac72e05a-c0c7-424b-b88d-239012160529 29/05/2016 12:52 479ce2e6-d3ea-4388-b8d2-31d51ff881be 27/05/2016 23:20 bp-a6aa4a07-1c31-43cf-b8d1-cdc4c2160527 27/05/2016 16:13 bp-90f037a4-387f-4607-a362-7a0e62160527 27/05/2016 15:40 a993be18-6d88-4703-b862-12904d122d88 26/05/2016 20:13 bp-006b70f7-32d8-445e-9407-b9cf52160525 25/05/2016 17:02 bp-52b43bd6-7894-4eba-a05a-3ad782160525 25/05/2016 15:13 ad3cbde2-bb8c-445c-b4b3-6e964331ab7e 25/05/2016 08:51 e5f286a1-e911-4957-aea8-2a629b7aa314 24/05/2016 20:53 bp-a0a1080a-8ea8-49a3-a454-a0fc62160523 23/05/2016 22:15 bp-d83377f2-76be-4a7a-9625-b01a42160521 21/05/2016 08:47 bp-c5515462-2b96-4d25-b7d3-25b522160512 13/05/2016 06:29 bp-a364145e-e8af-445c-bce5-c1fbb2160511 12/05/2016 06:05 bp-19810f30-9388-4197-9a0f-9ac132160511 11/05/2016 17:16 bp-1925fefd-7a88-43e0-a2a5-bb0c22160509 09/05/2016 07:09 bp-b320abb6-e3d1-4740-a73d-144de2160506 06/05/2016 18:35 bp-40dcfbd5-4fa7-4679-94ba-c71a22160505 05/05/2016 20:41 bp-e66280b7-2cf5-4d5a-9bb8-a019a2160503 04/05/2016 06:45 bp-e93dc711-90bb-40f2-8284-4d3c22160502 02/05/2016 15:29 bp-fbdb72a5-fe67-4ac9-8e47-d85ef2160501 01/05/2016 17:52 bp-78a08891-d2b3-4bef-bbc8-b5eac2160501 01/05/2016 10:12 651e3316-bd8e-4980-8fd1-8f055f4393df 01/05/2016 07:21
Все ответы (7)
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...