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

Firefox becomes non-responsive, 40% CPU, 1.6 Gb private, then crashes

  • 55 replies
  • 4 have this problem
  • Last reply by bsfinkel

more options

I am running Firefox (always the latest non-beta) in Windows 7 Professional 32-bit. I ALWAYS run with add-ons disabled. After a while (depending upon my usage of FF), but usually every day or every other day, FF becomes "non-responding". I have no idea what that term means in MS WIndows terms. When this happens, FF begins using up to 50% of the CPU, and is using 1.4 Gb of private space. When this happens sometimes the software will allow me to click "Exit" to terminate FF. Other times Windows will not allow me to click "Exit, andI have to use the Task Manager to cancel the firefox,.exe process. And, more times that not, when I am able to click Exit, Firefox takes a few minutes terminating before it crashes and gives me the option to cancel FF or restart it. I always send the dump to Mozilla. I have not looked at the recent crash reports.

This happened this morning about 15 minutes ago, and FF is behaving properly now. But it is already using 1.1 Gb of private space. i do not know if this private space usage is related to the problem. I do have11 FF windows in my current setup, as I use a different window for each project on which I am working. But so far I have only accessed two of the windows since the restart. I assume, that based on my projected usage of FF today, by tomorrow morning FF will have crashed by itself or I will have to Exit and restart.

What is happening? In MS terms, what is happening when a process becomes "non-responsive"? Is there some resource shortage that causes this? And when this happens, how can I debug FF and get more diagnostics? My records show that this has been occurring for over a year. Thanks.

All Replies (20)

more options

What you describe, slowness and "non-responding" mostly means the computer's CPU is being overworked.

Separate Issue; Your System Details shows;

Installed Plug-ins

Shockwave Flash 18.0 r0 Shockwave Flash 16.0 r0 Shockwave Flash 21.0 r0 Shockwave Flash 19.0 r0
Having more than one version of a program may cause issues. You must remove the older programs. Then get the current full installer.

Flash: Grab the uninstaller from here: Uninstall Flash Player | Windows Uninstall Flash Player | Mac

Then reinstall the latest version.

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: Flash Player (Linux) Version Direct link scans current system and browser Note: Other software is offered in the download. Step 1: Select Operating System Step 2: Select A Version (Firefox, Win IE . . . .) Note: Other software is offered in the download.

After the above, if there is still a problem; Start Firefox in Safe Mode {web Link} by holding down the <Shift>
key, and then starting Firefox. Is the problem still there?

more options

i have installed the latest Flash player, and I try to check every morning to see if there are any updates. I looked at the "uninstall flash" page, and I determined that it probably would not uninstall vestiges of previous Flash installs. So I went to C:\Windows\System32\Macromed\Flash and I renamed all files that had previous versions in their filenames. Then I exited and restarted Firefox.

about;add-ons - Plugins now shows me

Shockwave Flash 21.0.r0 and when i click on "more": NPSWF32_21_0_0_213.dll

I am not sure if the current Flash was using the older


files, and I do not know why the Flash install software dd not rename these old files. These older files have now been renamed (.renamed suffix appended), so they can no longer be used as .dll, .exe. and .ocx files.

I do not know if this was contributing to my problem.

more options

What about the CPU problem? Have you tried Safe Mode?

more options

By "Safe Mode" doyoume an running FF in safe mode or booting in safe mode. If the former, then re-read my initial statement of my problem. I ALWAYS run FF with add-ons disabled (unless FF starts in normal mode, at which time I switch to safe mode as soon as FF allows me to do so).

--Barry Finkel

more options

I've called the big guys to help you. Good luck.

more options

I have an idea. Would anyone want my previous.js, recovery.js, and/or recovery.bak files? Some tester could load one or more of these files on a test machine just to see what Firefox does. When I restarted Firefox yesterday, the private store usage was 1.1 Gb almost immediately.

I do not want to post them here, but I will send them privately to a tester.


--Barry Finkel

more options

Is the file text only? And not huge?

Open a text / word program and load the file. Left click once. Now <Control> A to highlight everything, then <Control> C to copy it.

Next have your browser go to; Paste <Control> P the content of the file in the window. Note: On the bottom, choose to save the file 30 days.

Now press Send. The page will reload. Copy the new web address, and post it here.

Remember to label each file.

more options

The three files


are mainly text files, but I cannot cut-and-paste them into the pastebin page. I tried a few times, and during my last attempt, FF crashed after being up about 3.5 hours. I believe that if I were able to put the files on pastebin, the files will not be extractible and re-created with their original names and loadable into Firefox. When I loaded one of the .js files into vim, that editor treated the file as having one line. I ran the "wc" utility on each if the three files, and that utility reported 0 lines. The file has no <cr-lf> characters, as an PC ASCII text file would contain.

Is there somewhere else where I can place one or all of these files? Thanks.

--Barry Finkel

more options

I don't know.

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.

more options

Here are the reports for April and May:

Submitted Crash Reports Report ID Date Submitted bp-e75c268d-e90f-4b22-a3cb-83b802160527 5/27/2016 1:59 PM bp-43d21ded-3762-40b5-916e-fdfd92160527 5/27/2016 10:31 AM bp-892247c0-f3d5-4dbc-9275-5d6312160526 5/26/2016 11:21 AM bp-8cbf7dd4-67ff-43bb-8128-4e5592160526 5/26/2016 11:18 AM bp-95d1216a-6af1-40d0-b7ce-499aa2160526 5/25/2016 8:03 PM 9186d79f-ee56-43b4-9646-37b3dd3ec117 5/25/2016 6:25 PM bp-25ec270d-6a3c-4173-92c0-792612160525 5/25/2016 8:33 AM bp-55947ad7-6cc6-4ca9-a352-00cf52160523 5/22/2016 9:07 PM bp-44645ae6-5910-4882-a250-3e4822160522 5/22/2016 9:18 AM 5c85792e-78d2-4ce4-89bf-37dbbade237e 5/19/2016 8:55 AM bp-e971e0b1-c091-4fca-a0d7-d1b132160516 5/16/2016 12:35 PM bp-aaf766ef-7e79-4e17-b4f1-ceaa62160515 5/15/2016 3:07 PM bp-637efc8e-294d-4d0d-9c10-baf592160512 5/12/2016 2:05 PM 863c04e5-a080-4935-be72-6ac85bc0626d 5/12/2016 7:42 AM bp-31cd02ac-31aa-4d46-a964-fcc202160509 5/9/2016 9:08 AM bp-43365ac7-03d5-4660-8f00-16ca82160506 5/5/2016 9:14 PM fc9e5837-6fb3-48b0-b5b5-86dcdb7ac76d 5/5/2016 9:11 PM bp-94fbeb0c-fdbb-4771-9e59-31b7d2160505 5/5/2016 9:14 AM 32dc5320-f967-484a-94a0-0b4318aa13a6 5/4/2016 4:06 PM 5c8b0b9a-a68b-4e7f-9f1b-3469ee3dff4c 5/4/2016 4:06 PM a2bd00fc-d7f2-46c1-9d6f-3cdb7f8cb4d3 5/4/2016 4:05 PM bp-1a132af2-b734-4e2b-b44d-dff3e2160503 5/3/2016 4:09 PM 53f80b78-94f8-47ca-9c4c-5274437adfaa 5/3/2016 1:35 PM bp-57c17205-8927-45fa-9830-f42fe2160503 5/3/2016 10:55 AM 8ecaa5c6-5a0e-4f2a-b58b-80791be7776e 5/2/2016 10:58 PM bp-0fb1f6ba-cb63-4d16-b6a3-39cbc2160502 5/2/2016 8:29 AM bp-fddfdbca-b3e0-4a99-8e91-880a82160501 4/30/2016 11:20 PM bp-b180ae41-ca60-4cb0-9cd7-997a02160428 4/28/2016 2:54 PM bp-2cbbc168-57bc-4bc6-84d6-ad18c2160427 4/27/2016 7:47 AM b5ffff72-5908-4daf-a4d7-17164e39c596 4/26/2016 8:14 AM bp-d4153326-b699-4ef6-8ba9-288162160425 4/25/2016 8:02 AM bp-02a1a216-2d5b-4f56-92bc-671aa2160422 4/22/2016 3:01 PM bp-4ffb912e-f278-4b88-8b63-a10d02160421 4/20/2016 10:55 PM 5ada3e4a-9a02-4d5a-997e-4c27dd12d2c8 4/20/2016 4:32 PM bp-8c936e42-d088-432f-ad53-4cf422160420 4/20/2016 3:41 PM 7ae1c7f7-be63-4b7b-b8e1-1e08642fc520 4/20/2016 3:36 PM 34dd4d40-dbaa-4144-a5fa-75e9f54a6cd6 4/20/2016 11:40 AM bp-304d42c5-ac9e-4b7e-b6a5-a90542160419 4/19/2016 10:03 AM f84f98c1-ccc2-4c7e-8330-817f0930abe3 4/19/2016 9:59 AM a9bbc0ea-e9d5-4dae-9a42-96e931d230d4 4/14/2016 2:52 PM 68a42cd3-0a7b-45cd-a576-9363824bec07 4/14/2016 2:52 PM 0971f1a9-6a38-4ad6-9048-200c2250529e 4/12/2016 9:42 PM a4846951-e102-4448-953e-8adcd6b9a7eb 4/12/2016 8:03 PM bp-7b28c97c-8f25-4ba2-8cf9-c3aa62160411 4/11/2016 3:39 PM bp-6318a3df-1269-40d6-bca0-2d7682160410 4/10/2016 9:06 AM bp-73259dd2-29b8-460d-8ca0-4fe802160408 4/8/2016 2:45 PM bp-c08b267a-9704-4469-88a6-57e8d2160405 4/5/2016 4:58 PM bp-f625c20f-779f-43b6-a492-f32ab2160405 4/5/2016 11:18 AM bp-f65f6245-96bc-4f4b-906b-1d2302160405 4/4/2016 8:06 PM bp-a1bfe61b-e1ef-40d0-a191-840252160404 4/4/2016 8:17 AM bp-f1c29371-7503-4383-a013-22dcc2160401 4/1/2016 3:49 PM

Note that I have not reviewed any of these dumps. I believe that each one occurred with the then-current non-beta version, as I tend to install a new version of FF as soon as I see it.

--Barry finkel

more options

You can look them over, but knowing how to read them is another thing.


Signature: OOM | large | mozalloc_abort | mozalloc_handle_oom | moz_xrealloc | winShmLock

Total Virtual Memory 2147352576

Available Virtual Memory 305410048

System Memory Use Percentage 94

Available Page File 615784448

Available Physical Memory 208560128

OOM Allocation Size 9437184

WRusr.dll = Webroot SecureAnywhere ++++++++++++++++++++++++++++++++++++++++++++++++++ bp-43d21ded-3762-40b5-916e-fdfd92160527

Signature: OOM | small

System Memory Use Percentage 94

Attention Sumo's there are 40 related bug reports

WRusr.dll = Webroot SecureAnywhere ++++++++++++++++++++++++++++++++++++++++++++++++++ bp-892247c0-f3d5-4dbc-9275-5d6312160526 bp-95d1216a-6af1-40d0-b7ce-499aa2160526

Signature: InternalFindAtom

System Memory Use Percentage 77

WRusr.dll = Webroot SecureAnywhere

This is for Sumo's Related Bugs 723133 VERIFIED FIXED Crash Report [@ PluginWndProcInternal ] stack overflow from infinite recursion

680862 RESOLVED FIXED Flash plugin crashes

564391 RESOLVED WORKSFORME crash when I'm going to view Ogg Theora format video on full screen mode [@ InternalFindAtom] +++++++++++++++++++++++++++++++++++++++++++++++++++ bp-8cbf7dd4-67ff-43bb-8128-4e5592160526

Signature: hang | wrusr.dll@0x1ca48

Process Type plugin Shockwave Flash Version:

NPSWF32_21_0_0_242.dll = Shockwave Flash = Adobe Systems

WRusr.dll = Webroot SecureAnywhere

xul.dll = Firefox

icudt56.dll = International Components for Unicode = The ICU Project +++++++++++++++++++++++++++++++++++++++++++++++++++++ bp-25ec270d-6a3c-4173-92c0-792612160525

Signature: StatsCompartmentCallback

System Memory Use Percentage 92

WRusr.dll = Webroot SecureAnywhere ++++++++++++++++++++++++++++++++++++++++++++++++++ bp-55947ad7-6cc6-4ca9-a352-00cf52160523 bp-44645ae6-5910-4882-a250-3e4822160522

Signature: hang | BaseGetNamedObjectDirectory | MsgWaitForMultipleObjects | F_1152915508

Process Type plugin Shockwave Flash Version:

more options

You have several different type crashes

Disable / update Webroot

If you have problems with current Shockwave Flash plugin versions then check this:

  • see if there are updates for your graphics drivers

  • disable protected mode in the Flash plugin (Flash 11.3+ on Windows Vista and later)

  • disable hardware acceleration in the Flash plugin See also:

more options

As you posted the above reports, you can now clean out the old reports.

In the address bar, type about:crashes<enter>. At the upper right, press the Remove All Reports button.

more options

I have a number of things in this reply. First, I was an IBM mainframe systems programmer for 25+ years, and my job was to read dumps of system and application crashes. But I do not know enough about the internals of Windows nor of Firefox to be able to interpret what each crash summary is telling me.

It is not clear from the summaries posted above that the problems are. Some of the summaries reference WRusr.dll, which is part of Webroot Secure Anywhere. I cannot tell from the summaries how WRSA is involved in the crashes, so I cannot pursue this with Webroot. I believe that my WRSA installation is up-to-date.

As for Adobe Flash plugin - I try to check once a day to ensure that my Flash is up-to-date, as Adobe frequently releases patches. I checked my Flash settings, and I do NOT have Flash using graphics hardware acceleration. I believe that the only window that I know uses Flash is a NOAA radar image window. And that window is constantly cycling through and updating the radar images. Other pages might use Flash to display ads, but normally after I have read the content of those pages, I close the pages. I do get warnings that "Flash has become unresponsive", and normally click "continue", unless the warning windows continue, at which time I click "cancel".

In the "TemporaryWorkaround" hyperlink above, there are two problems discussed:

 1)   Flash content does not appear
 2)   RealPlayer is not installed, Flash Player crashes in Firefox

Neither appears to be a problem that I am noticing, and I am not sure how that URL content applies to any Firefox dumps that i have experienced.

As for my graphics card driver - I installed a new Asus graphics card on March 11, and I believe that the drivers are up-to-date. My previous nVIDIA graphics card was frequent causing TDR timeout (116) BSODs, and I assume that the problem was in the nVIDIA graphics driver.

--Barry Finkel

more options

bsfinkel said

I cannot tell from the summaries how WRSA is involved in the crashes, so I cannot pursue this with Webroot. I believe that my WRSA installation is up-to-date.

FredMcD said

Disable / update Webroot
more options

I still am unsure as to why FF is crashing all the time. I cannot communicate with Webroot unless I know somewhat how WRSA is involved in any of the crashes. I cannot tell them, "I think that WRSA is involved in one or more of my FF crashes".

On some of the crash reports, I see possible errors listed. Some are underlined and some have a line through the bug ID number. What is the significance of these two notations? Does one signify that the bug has been eliminated as the cause, and the other means that the bug may be the cause?

I will repeat the suggestion I made earlier - I will gladly send one or more of my three restore files to any FF support personnel who wish to test them. I assume that if FF is started with my setup, then the NOAA radar image is started in my home page, then FF is left to sit untouched for 24-48 hours, FF will probably start acting up in the way that caused me to open this problem report. I babysit a Windows 8.1 64-bit laptop, and as a test I might copy the three restore files to that machine and run the test of FF. I do not know if the difference in OS or the difference in bits (32-bit vs 64-bit) would affect the test results. I do not want to attach any of these three files to this problem report.

--Barry Finkel

more options

Here is what i did this morning as a test: I copied my recovery.js file from my Windows 7 system to a Windows 8.1 64-bit laptop that I "babysit". I started Firefox with that recovery file, and I am going to let the system run untouched for 24 hours to see what happens to Firefox. I do not know if Firefox will behave differently on the laptop due to the change in OS or the fact that the laptop is running 64-bit. I will report the results when I have them.

I still want to know about the notations on a crash report - what is the significance of a bug number that is underlined vs. one that has the dashes placed in the middle of the bug number. Thanks.


more options

bsfinkel said

I still want to know about the notations on a crash report - what is the significance of a bug number that is underlined vs. one that has the dashes placed in the middle of the bug number. Thanks.

I believe they are lined through when they have been closed in the bug tracking system. Bugs can be closed when they are fixed, or if they are duplicates, or if they are impossible to solve, or if the behavior is considered correct and the remedy is to prevent a third party component from running.

More generally, Firefox tends to retain a significant amount of content in memory as you browse, including a pre-rendered version of a previously visited page you could go "back" to in a tab, and for some closed tabs. Over time, you may find it impossible to knock down the memory usage significantly because of this retained data. In some cases, this could be due to a flaw in Firefox that is triggered by certain conditions (such as only allowing a page to load partially); over time more of these bugs are fixed, but with new features, more are created.

On my 64-bit system, it's dangerous to get much over 2GB of memory use: Firefox becomes sluggish, some tabs do not paint correctly, and I may see NOT RESPONDING in the title bar. This seems to be much more of an issue with pages that feature "endless loading" such as the Facebook news feed than with ordinary pages. When I start to see this, I always try to exit normally as you do, but sometimes I do get the shutdown hang crash because for one reason or another, the time allotted for closing all connections and updating settings files runs out. These crashes appear to be hard to solve as there are numerous different flavors of them lingering in the bug tracking system.

Usually after a restart (either through exit or through a crash), Firefox only reloads the active tab in each window. If you have Firefox set to rebuild ALL open tabs, then you may indeed find yourself above 1GB again quickly. If you have Firefox set to reload all tabs but you keep a lot of tabs open only for occasional use, you could try to return to the default behavior. See the "Don’t load tabs until selected" setting here: Startup, home page, tabs, and download settings.

more options

I do not have FF open all tabs in all windows; FF opens only one tab in each window.

My test with my restore.js file on the Win 9.1 64-bit laptop ran for 48 hours, and FF did not exhibit any problems. FF private usage went almost immediately to 1.4 Gb, and it stayed there during the entire test. CPU usage was minimal, except those few seconds when the NOAA radar image was refreshing. But this test might not be valid due to the difference in OS and bit size. I will run a different test on Win 7 this weekend and report the results next week.

--Barry Finkel

more options

Here is another update. I restarted FF last Friday (06/10) at 4:55PM. I started the NOAA radar image window to update on its regular schedule. And there is another mail window that, I believe, updates automatically. I was not at the computer until last night (06/13) at 9:20PM. I looked at FF, and it was behaving properly. This morning I used FF for a while until noon; I saw no problems. At noon I started my Patch Tuesday maintenance, and at 13:33 I rebooted after installing the MS patches. Before the reboot, I Exited all of my running processes, including FF. FF crashed during its termination process.


I looked briefly at the crash report, but I do not know for what to look to determine why FF crashed.

I will be using FF this evening to see if it misbehaves.

--Barry Finkel

  1. 1
  2. 2
  3. 3