X
Tap here to go to the mobile version of the site.
Your Firefox is out of date and may contain a security risk! Upgrade Firefox

Support Forum

Firefox 17 huge memory leak

Posted

Since the last update today, Firefox seems to got a huge memory leak. After one hour idle on some pages it was up to 750MB memory usage, and constant 100% load of one CPU core.

Looks like something is not going well with the garbage collection, if I visit http://www.robertsspaceindustries.com/forums/forum/forum-category-2/ for example.

Had to disable the graphic hardware acceleration, because of the newly introduced "clear type" font bug.

Edit: May also be related to mail.google.com, which I have running in an app tab.

Modified by BoMbY

Additional System Details

Installed Plug-ins

  • Shockwave Flash 11.5 r502
  • 1.140.0
  • 0.70.4
  • Adobe PDF Plug-In For Firefox and Netscape 10.0.0

Application

  • User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/17.0 Firefox/17.0

More Information

Application Basics
Name
Firefox
Version
17.0
User Agent
Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/17.0 Firefox/17.0
Profile Folder
Show Folder
Enabled Plugins
about:plugins
Build Configuration
about:buildconfig
Crash Reports
about:crashes
Memory Use
about:memory
Extensions
Name
Version
Enabled
ID
Adblock Plus
2.2
true
{d10d0bf8-f5b5-c8b4-a8b2-2b9879e08c5d}
DownloadHelper
4.9.12
true
{b9db16a4-6edc-47ec-a1f4-b86292ed211d}
Live HTTP headers
0.17
true
{8f8fe09b-0bd3-4470-bc1b-8cad42b8203a}
Status-4-Evar
2012.07.08.17
true
status4evar@caligonstudios.com
Convergence
0.09
false
convergence@extension.thoughtcrime.org
NoScript
2.6.2rc1
false
{73a6fe31-595d-460b-a920-fcc0f8843232}
Important Modified Preferences
Name
Value
accessibility.typeaheadfind.flashBar
0
browser.cache.disk.enable
false
browser.cache.disk.smart_size.first_run
false
browser.cache.disk.smart_size_cached_value
1048576
browser.history_expire_days.mirror
180
browser.history_expire_days_min
31
browser.places.importBookmarksHTML
false
browser.places.smartBookmarksVersion
4
browser.privatebrowsing.dont_prompt_on_enter
true
browser.startup.homepage
about:robots
browser.startup.homepage_override.buildID
20121119183901
browser.startup.homepage_override.mstone
17.0
browser.tabs.warnOnClose
false
extensions.lastAppVersion
17.0
gfx.direct2d.disabled
true
gfx.direct3d.prefer_10_1
true
layers.acceleration.disabled
true
network.cookie.prefsMigrated
true
places.database.lastMaintenance
1353145252
places.history.expiration.transient_current_max_pages
104858
places.history.expiration.transient_optimal_database_size
167772160
places.last_vacuum
1306008450
print.print_printer
Samsung CLX-3170 Series
print.printer_CutePDF_Writer.print_bgcolor
false
print.printer_CutePDF_Writer.print_bgimages
false
print.printer_CutePDF_Writer.print_command
print.printer_CutePDF_Writer.print_downloadfonts
false
print.printer_CutePDF_Writer.print_edge_bottom
0
print.printer_CutePDF_Writer.print_edge_left
0
print.printer_CutePDF_Writer.print_edge_right
0
print.printer_CutePDF_Writer.print_edge_top
0
print.printer_CutePDF_Writer.print_evenpages
true
print.printer_CutePDF_Writer.print_footercenter
print.printer_CutePDF_Writer.print_footerleft
&PT
print.printer_CutePDF_Writer.print_footerright
&D
print.printer_CutePDF_Writer.print_headercenter
print.printer_CutePDF_Writer.print_headerleft
&T
print.printer_CutePDF_Writer.print_headerright
&U
print.printer_CutePDF_Writer.print_in_color
true
print.printer_CutePDF_Writer.print_margin_bottom
0.5
print.printer_CutePDF_Writer.print_margin_left
0.5
print.printer_CutePDF_Writer.print_margin_right
0.5
print.printer_CutePDF_Writer.print_margin_top
0.5
print.printer_CutePDF_Writer.print_oddpages
true
print.printer_CutePDF_Writer.print_orientation
0
print.printer_CutePDF_Writer.print_pagedelay
500
print.printer_CutePDF_Writer.print_paper_data
9
print.printer_CutePDF_Writer.print_paper_height
11,00
print.printer_CutePDF_Writer.print_paper_size_type
0
print.printer_CutePDF_Writer.print_paper_size_unit
1
print.printer_CutePDF_Writer.print_paper_width
8,50
print.printer_CutePDF_Writer.print_reversed
false
print.printer_CutePDF_Writer.print_scaling
1,00
print.printer_CutePDF_Writer.print_shrink_to_fit
true
print.printer_CutePDF_Writer.print_to_file
false
print.printer_CutePDF_Writer.print_unwriteable_margin_bottom
0
print.printer_CutePDF_Writer.print_unwriteable_margin_left
0
print.printer_CutePDF_Writer.print_unwriteable_margin_right
0
print.printer_CutePDF_Writer.print_unwriteable_margin_top
0
print.printer_Samsung_CLX-3170_Series.print_bgcolor
false
print.printer_Samsung_CLX-3170_Series.print_bgimages
false
print.printer_Samsung_CLX-3170_Series.print_command
print.printer_Samsung_CLX-3170_Series.print_downloadfonts
false
print.printer_Samsung_CLX-3170_Series.print_edge_bottom
0
print.printer_Samsung_CLX-3170_Series.print_edge_left
0
print.printer_Samsung_CLX-3170_Series.print_edge_right
0
print.printer_Samsung_CLX-3170_Series.print_edge_top
0
print.printer_Samsung_CLX-3170_Series.print_evenpages
true
print.printer_Samsung_CLX-3170_Series.print_footercenter
print.printer_Samsung_CLX-3170_Series.print_footerleft
&PT
print.printer_Samsung_CLX-3170_Series.print_footerright
&D
print.printer_Samsung_CLX-3170_Series.print_headercenter
print.printer_Samsung_CLX-3170_Series.print_headerleft
&T
print.printer_Samsung_CLX-3170_Series.print_headerright
&U
print.printer_Samsung_CLX-3170_Series.print_in_color
true
print.printer_Samsung_CLX-3170_Series.print_margin_bottom
0.5
print.printer_Samsung_CLX-3170_Series.print_margin_left
0.5
print.printer_Samsung_CLX-3170_Series.print_margin_right
0.5
print.printer_Samsung_CLX-3170_Series.print_margin_top
0.5
print.printer_Samsung_CLX-3170_Series.print_oddpages
true
print.printer_Samsung_CLX-3170_Series.print_orientation
0
print.printer_Samsung_CLX-3170_Series.print_page_delay
50
print.printer_Samsung_CLX-3170_Series.print_paper_data
9
print.printer_Samsung_CLX-3170_Series.print_paper_height
11,00
print.printer_Samsung_CLX-3170_Series.print_paper_size_type
0
print.printer_Samsung_CLX-3170_Series.print_paper_size_unit
1
print.printer_Samsung_CLX-3170_Series.print_paper_width
8,50
print.printer_Samsung_CLX-3170_Series.print_reversed
false
print.printer_Samsung_CLX-3170_Series.print_scaling
1,00
print.printer_Samsung_CLX-3170_Series.print_shrink_to_fit
true
print.printer_Samsung_CLX-3170_Series.print_to_file
false
print.printer_Samsung_CLX-3170_Series.print_unwriteable_margin_bottom
0
print.printer_Samsung_CLX-3170_Series.print_unwriteable_margin_left
0
print.printer_Samsung_CLX-3170_Series.print_unwriteable_margin_right
0
print.printer_Samsung_CLX-3170_Series.print_unwriteable_margin_top
0
privacy.cpd.cookies
false
privacy.cpd.downloads
false
privacy.cpd.formdata
false
privacy.cpd.history
false
privacy.cpd.sessions
false
privacy.sanitize.migrateFx3Prefs
true
privacy.sanitize.timeSpan
0
security.warn_viewing_mixed
false
Graphics
Adapter Description
NVIDIA GeForce GTX 670
Vendor ID
0x10de
Device ID
0x1189
Adapter RAM
2048
Adapter Drivers
nvd3dumx,nvwgf2umx,nvwgf2umx nvd3dum,nvwgf2um,nvwgf2um
Driver Version
8.17.13.142
Driver Date
5-15-2012
Direct2D Enabled
false
DirectWrite Enabled
false (6.1.7601.17789)
ClearType Parameters
Gamma: 2200 Pixel Structure: RGB ClearType Level: 100 Enhanced Contrast: 50
WebGL Renderer
Google Inc. -- ANGLE (NVIDIA GeForce GTX 670) -- OpenGL ES 2.0 (ANGLE 1.0.0.1242)
GPU Accelerated Windows
0
AzureCanvasBackend
cairo
AzureFallbackCanvasBackend
none
AzureContentBackend
none
JavaScript
Incremental GC
1
Accessibility
Activated
0
Prevent Accessibility
0
Library Versions
Expected minimum version
Version in use
NSPR
4.9.2
4.9.2
NSS
3.13.6.0 Basic ECC
3.13.6.0 Basic ECC
NSS Util
3.13.6.0
3.13.6.0
NSS SSL
3.13.6.0 Basic ECC
3.13.6.0 Basic ECC
NSS S/MIME
3.13.6.0 Basic ECC
3.13.6.0 Basic ECC

cor-el
  • Top 10 Contributor
  • Moderator
10747 solutions 96705 answers

One or more extensions may not be working properly.

Did you try to run Firefox in Safe mode?


Try to create a new profile as a test to check if your current profile is causing the problems.

See "Creating a profile":

There may be extensions and plugins installed by default in a new profile, so check that in "Tools > Add-ons > Extensions & Plugins" in case there are still problems.

If the new profile works then you can transfer some files from the old profile to that new profile, but be careful not to copy corrupted files.

Question owner

Yeah, the add-ons worked fine before the update to FF17. This is two new bugs for me in this version. Getting worse with every version now - I think I'll give Opera a try first. You really should scrap everything since version 3.6, and start new from there.

cor-el
  • Top 10 Contributor
  • Moderator
10747 solutions 96705 answers

It is always possible that extensions aren't working properly after an update. Not every possible combination of extensions can be tested, so this may get unnoticed before a new versions gets released to a larger public.

OneAhead 0 solutions 3 answers

Helpful Reply

For what it's worth, I had exactly the same problem (except that it's on Linux) since the upgrade to 17.0. When I disabled greasemonkey, the problem instantly disappeared, so it looks like the compatibility with greasemonkey got broken.

Likewise, I'm very disappointed with the frequent bugs/annoyances that come with the rolling upgrade system; I find myself more and more using Chromium because of it. Mozilla really needs to give people the option to run a stable branch that receives security updates only.

Matt_G
  • Administrator
  • Moderator
380 solutions 1848 answers

BoMby,

Were you able to identify if it was a particular extension causing the issue? If we can identify what is causing the problem, we can sometimes help by working with the 3rd party. Please let us know if you find anything.


@OneAhead

I looked into your greasemonkey report. I'm assuming it was an individual greasemonkey script and not GM itself, is that correct?

StevenCee 0 solutions 50 answers

Helpful Reply

Really now, can't the developers at least try the most common extensions & add-ons people use, see if they work ok, BEFORE releasing new updates??? Why must we go through some laborious process, individually, EVERY time a new update is released, just to see why it still sucks up RAM, freezes, stalls & crashes?

BuffaloJohn 0 solutions 1 answers

The curious thing I have noticed is that there seems to be a disconnect between what FF17 knows about memory and what Windows knows. I can get FF all wadded up with gobs of memory after hours of using it. I tend to open and close lots of tabs.

I have tried all the things mentioned in every post on this subject and nothing makes a difference. It's not about any one thing, it is something internal. My latest experiment seems to confirm that. I got into a state where about:memory was showing FF at 1.2GB and the task manager in Windows seemed to support that. There is the application memory and there is the commit charge. Normally, when I boot new and no apps have been loaded, there is about 800MB in commit charge. When FF gets wadded up, it is usually 2.4GB there. About:memory usually shows the delta between all the other apps and FF. So far so good. So, now I closed all tabs but did not exit FF and left only about:memory loaded. After waiting 30 minutes, a:m shows still 1.2GB, but the commit charge has dropped to 1.6GB. That is below the level before any app starts, so FF is thinking it has a boatload of memory that the OS no longer thinks it has. No matter how many times I try to do GC or CC or Minimize_Memory, it is stuck at 1.2GB. FF has clearly lost track of memory. The OS still thinks it has 622MB, which is close to the delta between no apps and Commit Charge, and yet FF thinks it has double that.

My guess is that one of two things will now happen when I try to close FF. First, it will crash because it will try to access memory that has already been released. Or Second, it will spin the disk for the next 20 minutes paging in stuff that should have been released ages ago.

<<<Closed actually pretty quickly, I was wrong. Commit went to 823MB. Restarted FF and commit went to 966 and a:m showed 260MB v-size and the task manager shows FF at 136MB>>>

I know that if I disable all extensions and add-ons, the problem goes away, but that is only because FF is unusable at that point. I have to have the add-ons to make it usable. There is too much junk to block.

Modified by BuffaloJohn

OneAhead 0 solutions 3 answers

@Matt_G

Sorry for my late reply. The Greasemonkey scripts I have on my system are "Youtube to me" and "Google Search - Remove Redirection 2.02". The latter never worked and the former I used so long ago I can't remember. Funny thing is that I got the memory issues even though the greasemonkey extension was set to "disabled" (ie. greasemonkey icon was there but in washed-out color), and the problem only went away when I disabled greasemonkey in the extensions manager (ie. no greasemonkey icon present anymore).

Apart from that, I'm also running NoScript, but that doesn't appear to be related to the problem (and I can't live without it anyway).

OneAhead 0 solutions 3 answers

One last piece of info: the problem was particularly pronounced when having a few tabs open on slashdot.org (which is heavy on JavaScript), bbc.co.uk and YouTube. The latter 2 would suggest a flash problem, but that wasn't the case; the plugin container's memory usage was not unusual and didn't change with removing greasemonkey. I even manually killed the plugin container at some point to see if the problem would go away and it didn't; it was really the firefox binary hogging up memory.

SoftTest123 0 solutions 1 answers

I am having this problem with FF 18.0.2, but I am also having the problem with Thunderbird so I think it is a Mozilla problem not specific to either program. Generally the problem is so severe that it brings my quad 64 bit processor to its knees, locking up with massive FF and TB page faults.

I, too, use lots of tabs and lots of windows. I'll probably switch to Chrome until the problem is fixed and delete all my tabs in TB and hope that allows me to work.

Right now I only have this one window of FF open with one tab and if memory is leaking it is too slow to notice over 1 minute.

John99
  • Top 25 Contributor
  • Moderator
622 solutions 8010 answers

SoftTest123,
Sorry you are having problems. It is probably unlikely to be a general Firefox problem.

If you want a solution it is probably best to start a new tread by asking your own question using /questions/new (And then post back here to cross link the new thread.)

You should also try Firefox in Firefox's SafeMode with all plugins disabled.

Note also that keying into the location bar about:memory brings up an interactive utility showing a lot of memory information, and includes a button to clear some of that  memory.