Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Lolu chungechunge lwabekwa kunqolobane. Uyacelwa ubuze umbuzo omusha uma udinga usizo.

Plugin container often takes 75 to 80% of memory even when all addon's have been removed/deactivated

  • 11 uphendule
  • 2 zinale nkinga
  • Igcine ukuphendulwa ngu gslrider

more options

I've been using Firefox for years...since early 2005 and it has been a dream. But recently it has started to crash and the Plugin container regularly uses 50% of my memory and this has increased to over 95% causing the computer to freeze altogether. Even trying to open task manager to close Firefox has on one occasion taken 20 minutes. This seems to have only recently started to happen since I "upgraded" to Firefox ver 49.0.2 I have tried installing earlier versions, but keep getting annoying popups to upgrade, so I've reinstalled 49.0.2. I know earlier versions may have security issues, but anything has to be preferable to the Plugin container taking over my computer. It still happens now, even thought I have disabled all my plugins/add-ons listed below I have an Acer laptop with 4Gb memory and running W 8.1 Help in resolving this would be appreciated Eddie

Isisombululo esikhethiwe

I found the following reports for Firefox 49 (the others were for versions 44 and lower):

Are my assumptions correct about when the crashes occur, or can you provide more context?

Funda le mpendulo ngokuhambisana nalesi sihloko 👍 1

All Replies (11)

more options 50.1

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.

(Please don't take a screenshot of your crashes, just copy and paste the IDs. The below image is just an example of what your Firefox screen should look like.)


more options

I have tried doing as you requested, but keep getting this message for some of the crash reports

We couldn't find the Crash ID you're after. If you recently submitted this crash, it may still be in the queue.

If you believe this message is an error, please submit a Bugzilla ticket describing what happened, and please include the URL for this page

The url for these reports are as follows

Is it 8.1 that is the problem, my other PC runs XP Pro and althought there is now "no support" it is in many respects a better more reliable OS. I cannot remember the last time that PC crashed Firefox and it only has 2Gb of memory. The revised list is now as follows

Report ID Date Submitted bp-77df342f-561c-4b89-8a4f-dd52b2161231 31/12/2016 12:06 bp-250709cd-d778-4dec-91a0-ff6452161231 31/12/2016 12:06 bp-994ecc91-2aa2-40d9-845a-7d91e2161231 31/12/2016 12:05 bp-568901f9-b5bb-4004-a349-0a58f2161231 31/12/2016 12:05 bp-4a0a566a-4283-4994-bfb4-a4a792161231 31/12/2016 12:04 bp-acedb994-fb77-4311-9569-7d87c2161231 31/12/2016 12:04 bp-c96bf431-37ba-471f-adc8-371eb2161231 31/12/2016 12:03 bp-747febe9-3a10-42c9-baa9-0a9572161231 31/12/2016 12:03 bp-beed861b-c462-4494-8503-9b7b02161231 31/12/2016 12:02 bp-e91bd6be-3c74-4999-a4d8-3e3d62161231 31/12/2016 12:02 bp-4a42aa04-a909-4b82-b5a1-bc80b2161231 31/12/2016 12:02 bp-185cd5be-cc4c-40dd-8ff1-aa75b2161231 31/12/2016 12:01 bp-f23aaa9b-4f39-4661-b3d8-779cc2161231 31/12/2016 12:01 bp-4f5b33ef-187a-4ffa-986f-329172161231 31/12/2016 11:59 bp-83c12717-d1cd-4ef7-8cd5-cc13c2161231 31/12/2016 11:58 bp-42f86964-f42c-4da2-92d7-d033c2161231 31/12/2016 11:56 bp-af893041-2f8c-4d61-929f-1b1e82161231 31/12/2016 11:56 bp-3c8a5c41-20f9-45bd-ae0e-b56992161231 31/12/2016 11:56 bp-7ce1bb2d-b6f4-4c6d-91bb-bd0302161231 31/12/2016 04:12 bp-cc524dbf-5502-40d4-af88-d26be2161231 31/12/2016 04:11 bp-57e1bcf7-d9b5-4d31-9a87-b88112161231 31/12/2016 04:11 bp-26afc422-470a-4721-baf7-81fa82161222 22/12/2016 16:19 bp-d880ede6-4e91-451d-9cce-96f612161114 14/11/2016 17:08 bp-e8926a71-0774-4d36-a375-53b6b2161101 01/11/2016 07:55 bp-b9172948-3734-4324-a8c0-63cb72161019 19/10/2016 08:33 bp-a3a3a717-69b1-48bd-9ab6-b81142160310 10/03/2016 00:05 bp-64f2b417-bc39-4496-a418-90cb62160307 07/03/2016 23:44 bp-0d5ba2db-ddbb-491b-93fa-4d74d2160307 07/03/2016 23:40 bp-2289299d-3f93-4e3b-8868-737dc2160307 07/03/2016 23:35 bp-64da30b0-f962-4e23-8363-98c982160302 02/03/2016 23:07 bp-3b3d492e-dbb5-4608-a5b7-3f0f92160302 02/03/2016 00:20 bp-abb9b071-bdd2-4626-980a-588c72160126 26/01/2016 08:11 bp-87856210-b5f2-468a-8053-85c902151221 21/12/2015 18:01 bp-c86d2980-55a4-4e54-a7fb-075bf2151127 27/11/2015 00:10 bp-8730b2c5-0e31-476c-8896-a44e32151126 26/11/2015 23:55 bp-9f2c03d2-ccbe-45b4-8e2b-f52142151112 12/11/2015 07:19 bp-790144a3-4df1-4071-ad71-944632151029 29/10/2015 22:06

more options

Product Firefox Release Channel release Version 49.0.2 Build ID 20161019084923 OS Windows 8.1 OS Version 6.3.9600 50.1

bp-4f5b33ef-187a-4ffa-986f-329172161231 Date Processed 2016-12-31 11:57:33

Signature: mozalloc_abort | NS_DebugBreak | mozilla::ipc::FatalError | mozilla::net::PNeckoChild::FatalError | mozilla::net::PNeckoChild::SendPHttpChannelConstructor

atidxx32.dll = Advanced Micro Devices = Check this link;

This is for Sumo's Related Bugs 1277582 RESOLVED FIXED PNeckoChild::SendPHttpChannelConstructor called during shutdown ++++++++++++++++++++++++++++++++++++++++++++++ Product Firefox Release Channel release Version 43.0 Build ID 20151208100201 OS Windows 8.1 OS Version 6.3.9600

bp-f23aaa9b-4f39-4661-b3d8-779cc2161231 Signature: hang | ConsoleCopyStringToBuffer

Date Processed 2016-12-31 11:59:28

Process Type plugin Shockwave Flash Version:

This is for Sumo's Related Bugs 1146350 NEW --- Crash in [@ hang | ConsoleCopyStringToBuffer ]

Security Issue: Update your Flash Player Note: Windows users should download the active_x for Internet Explorer. and the plugin for Plugin-based browsers (like Firefox).

Note: Windows 8 and Windows 10 have built-in flash players and Adobe will cause a conflict. Install the plugin only. Not the active_x.

Flash Player Version: Direct link scans current system and browser Note: Other software is offered in the download. <Windows Only> Step 1: Select Operating System Step 2: Select A Version (Firefox, Win IE . . . .) Note: Other software is offered in the download. <Windows Only>

See if there are updates for your graphics drivers

more options

Are the above reports I checked from two different computers?

more options

No, they are all from the same laptop. I ahve tried checking for updates as suggested in the last message from FredMcD, but unable to do so because I'm not the "Administrator"

........... even though I'm the only user and owned the laptop from new, for some reason I'm not the "Administrator" 


more options

An update. I have managed to work out how to find the hidden Administrator menu.................whats the point in hiding it and making it so hard to access? Anyway got there and doing this has allowed to download all the latest M S updates, 46 of them. The plugin container usage has reduced slightly from 75% to approx 50% But... I now have an additional problem not present before in that twice today I have had an "exceptional breakpoint" error message and the PC then shuts down. I hate 8.1, I think I'm going back to XP Pro

more options

XP is on its way out the door, I recommend Win 7. Check with where you got the computer.

I called for more help.

more options


Multiprocess (e10s)

One of the headline changes in Firefox 48+ is e10s, which separates the browser interface process from the page content process. More and more users are gradually having this multiprocess feature switched on. The performance impact of this can vary a lot between systems: many users find it faster, some find it slower, for many it's neutral.

e10s may cause either of these in the Windows Task Manager Processes tab (or on newest Windows, on the Details tab):

  • Second firefox.exe process
  • Single firefox.exe process and huge plugin-container.exe process

I don't know whether this is relevant to your experience, so let's check.

Are you using e10s?

You can confirm you have this feature turned on as follows. Either:

  • "3-bar" menu button > "?" button > Troubleshooting Information
  • (menu bar) Help > Troubleshooting Information
  • type or paste about:support in the address bar and press Enter

In the first table on the page, check the row for "Multiprocess Windows" and see whether the number on the left side of the fraction is greater than zero. If so, you are using e10s.

If you are using e10s:

If you think Firefox is not performing well or is using an unreasonable amount of resources now, you could evaluate whether e10s is causing this problem by turning it off as follows:

(1) In a new tab, type or paste about:config in the address bar and press Enter/Return. Click the button promising to be careful.

(2) In the search box above the list, type or paste autos and pause while the list is filtered

(3) Double-click the browser.tabs.remote.autostart.2 preference to switch the value from true to false

Note: the exact name of the preference may vary, but it will start with browser.tabs.remote.autostart

At your next Firefox startup, it should run in the traditional way. Any difference?

more options

Isisombululo Esikhethiwe

I found the following reports for Firefox 49 (the others were for versions 44 and lower):

Are my assumptions correct about when the crashes occur, or can you provide more context?

more options

Not sure exactly what I've done, but followed the suggestions regards e10s and changed the value in "browser.tabs.remote.autostart.2" to false and although the plugin container is still there, the usage is now very small and it appears to have resolved the problem. Thank you to everyone who has contributed, especially jscher2000 who seems to have find the solution to my issues.

Best regards to all


more options

This totally sounds like a memory issue within Firefox. Which is an old issue that's never been resolved. At least for me. And I've been using Firefox since before it was 4.0. That's when Firefox was awesome. Progressively got worse after 4.0.

I found a definite fix for my Firefox memory leak issue. I switched to Chrome. Seriously. Not by choice, but sheer necessity. Couldn't deal with how Firefox hogging memory was messing with my system. Yes, it was Firefox. Cuz when I quit Firefox, my system was happy again.

Since Firefox 4.0 came out, I've had memory leak issues (never a problem pre 4.0). And to this very day, still have memory leak issues. After 2 days of running Firefox it jacks up to using over 2GB of physical memory. 2GB!! I've tried all the tips. ALL THE TIPS. Let's make that clear. From forums to Firefox themselves. NOTHING works. NOTHING. Including the ones mentioned here. Then I finally found a fix! I switched to Chrome! Without having to jump through hoops or going into config and mucking around with settings. Plug and play if you will.

How do I know it was fixed, well let me tell you. I'm on a Mac system, I watch the memory usage on Activity Monitor. I loaded the same plug-ins and extensions that I used in Firefox, on to Chrome (lucky they had Chrome versions of them), and deleted the ones that weren't. So under the hood, when it came to plugins and extensions, they were the same. Both browsers are the latest versions. On a full reboot of my system. Then I did exactly the same things I've always done on Firefox on Chrome. Hitting the same sites, and downloading same files. Within 2 days, I checked Activity Monitor, Firefox was hitting around 1.7GB (started on launch at 487MB), Chrome...582MB (started on launch at 500MB). I let Chrome go without quitting for the rest of the week, and it never broke 600MB. And sometimes, it would even go down. Without me having to quit for it to release memory. THAT is how a browser should be dealing with memory. And really, it's neither faster or slower than Firefox.

I've never wanted to switch to Chrome, because I like the feel of Firefox better. As well, Firefox had better plugins/extensions and themes (imo). But now, they are on pretty much on par when it comes to those things. And although I still like the feel of Firefox better. I've gotten used to how Chrome feels. So not having memory issues anymore vs slightly better feel when using, is more than a fair trade off for me. Sorry Mozilla, but you had to go. Firefox just messes with my system, no matter what I do.

Anyone that still have issues with Firefox bogging your system because of memory leaks? Switch to Chrome.