cancel
Showing results for 
Search instead for 
Did you mean: 

Version 20, Memory Leak Still?

Highlighted
New User

Version 20, Memory Leak Still?

I've been using Firefox since well, lets just say long enough... Version 20 for the Mac seems to not have fixed any bugs or memory leaks.

One of the "fixes" is to restart Firefox, which is the only "fix" that works, but this really isn't a fix, this is a stopgap situation, in where you release the memory by closing it...

Are there other people with this same situation? My Firefox uses with nothing in the main page except google.com, if it's open for over 24 hours over 1GB of ram... 2 GB in 48 hours, etc...

The most Firefox has ever used was 5GB before I shut it down, now I know, restarting Firefox seems to stop this from happening, but as I said, this is a stopgap, there is something inside Firefox that makes this happen.

Is there anything in the future that will fix this issue, or is Firefox going to be forever a Memory Hog worse than Microsoft Office?

Tags (2)
104 REPLIES
Site Moderator

Re: Version 20, Memory Leak Still?

You can check the memory usage on the about:memory page.

New User

Re: Version 20, Memory Leak Still?

Yes, I know about that document, as I stated above the only thing that fixes it is restarting the program, which isn't a true fix, just a stop-gap.

Site Moderator

Re: Version 20, Memory Leak Still?

So, minimizing the memory usage by clicking the button on the about:memory page doesn't have effect?


Start Firefox in Safe Mode to check if one of the extensions (Firefox/Tools > Add-ons > Extensions) or if hardware acceleration is causing the problem (switch to the DEFAULT theme: Firefox/Tools > Add-ons > Appearance).

  • Do NOT click the Reset button on the Safe Mode start window or otherwise make changes.

Do a clean reinstall and delete the Firefox program folder before reinstalling a fresh copy of Firefox.

Download a fresh Firefox copy and save the file to the desktop.

Uninstall your current Firefox version, if possible, to cleanup the Windows registry and settings in security software.

  • Do NOT remove personal data when you uninstall your current Firefox version, because all profile folders will be removed and you will also lose your personal data like bookmarks and passwords from profiles of other Firefox versions.

Remove the Firefox program folder before installing that newly downloaded copy of the Firefox installer.

Your bookmarks and other profile data are stored in the Firefox profile folder and won't be affected by an uninstall and (re)install, but make sure that "remove personal data" is NOT selected when you uninstall Firefox.

If you keep having problems then also create a new profile.


Site Moderator

Re: Version 20, Memory Leak Still?

Hello,

The Reset Firefox feature can fix many issues by restoring Firefox to its factory default state while saving your essential information. Note: This will cause you to lose any Extensions, Open websites, and some Preferences.

To Reset Firefox do the following:

  1. Go to Firefox > Help > Troubleshooting Information.
  2. Click the "Reset Firefox" button.
  3. Firefox will close and reset. After Firefox is done, it will show a window with the information that is imported. Click Finish.
  4. Firefox will open with all factory defaults applied.

Further information can be found in the Refresh Firefox - reset add-ons and settings article.

Did this fix your problems? Please report back to us!

Thank you.

New User

Re: Version 20, Memory Leak Still?

@cor-el the only extension I have running is Ghostery, I have my cache cleaned out every day by a chron job, and through another app I use to keep my computer running smoothly. The Cache is not allowed to 50 MB, I have no Application Cache, and as you will see via the image this version of Firefox was installed a little over a month ago.

When I installed it, it was from a clean install. I used Amnesia to remove everything, including my personal data. I have everything on the cloud that I need so getting my personal info back was no issue.

Also, a heads up, I'm on a Mac. As my More System Information shows on the right of the screen.

User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_8_3) AppleWebKit/536.28.10 (KHTML, like Gecko) Version/6.0.3 Safari/536.28.10

This should not be happening with less than a month under the life of the App unless there is a memory leak. Restarting the App, Resetting the App, and going through the steps I have should of been more than enough to resolve this issue.

@philipp

As shown above I went beyond that, no go... I did a clean install a month ago, I really don't understand why this is happening. I can wipe out Firefox again, but seriously? Are you telling me once a month I got to blow away Firefox and re-install it to keep it "fresh and functional"...

That's not a fix, as I've said before, that is the ultimate stop-gap, one I will not tolerate. Safari is looking pretty good to me right now.

2013-04-28-05-11-36-1d3b92.png
New User

Re: Version 20, Memory Leak Still?

Also, the last time I posted about this, and it was a real issue was back in version 4, and was beta testing version 5. At that time over 700 people said they had the same issue. Want to wait a week or so and see how many more people have the same issue?

https://support.mozilla.org/en-US/questions/803094?esab=a&as=s&r=1&page=1

I don't see why after 16/15 versions this issue has not been resolved.

Site Moderator

Re: Version 20, Memory Leak Still?

the most common cause of memory leaks in firefox are third-party extensions. you didn't provide much information about your configuration though - please go to firefox > help > troubleshooting information & use the button to copy the contents of the page & paste them here into a forum reply...

New User

Re: Version 20, Memory Leak Still?

Here you go, there is nothing in my extensions except Avast! WebRep and Ghostery, that's it. Nothing fancy, and except one, I haven't stated before.

I am not an extension collector, I only use what I require. As you can see there is nothing truly out of place.

 Application Basics
       Name
       Firefox
       Version
       20.0
       User Agent
       Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:20.0) Gecko/20100101 Firefox/20.0
       Build Configuration
         about:buildconfig
 Extensions
       Name
       Version
       Enabled
       ID
       Ghostery
       2.9.4
       true
       firefox@ghostery.com
       avast! WebRep
       8.0.4451
       false
       wrc@avast.com
 Important Modified Preferences
     Name
     Value
       accessibility.typeaheadfind.flashBar
       0
       browser.cache.disk.capacity
       51200
       browser.cache.disk.smart_size_cached_value
       358400
       browser.cache.disk.smart_size.enabled
       false
       browser.cache.disk.smart_size.first_run
       false
       browser.cache.disk.smart_size.use_old_max
       false
       browser.places.smartBookmarksVersion
       4
       browser.startup.homepage
       www.google.com
       browser.startup.homepage_override.buildID
       20130326150557
       browser.startup.homepage_override.mstone
       20.0
       browser.tabs.warnOnClose
       false
       dom.mozApps.used
       true
       dom.w3c_touch_events.expose
       false
       extensions.lastAppVersion
       20.0
       font.language.group
       x-western
       font.minimum-size.ar
       12
       font.minimum-size.el
       12
       font.minimum-size.he
       12
       font.minimum-size.ja
       12
       font.minimum-size.ko
       12
       font.minimum-size.th
       12
       font.minimum-size.tr
       12
       font.minimum-size.x-armn
       12
       font.minimum-size.x-baltic
       12
       font.minimum-size.x-beng
       12
       font.minimum-size.x-cans
       12
       font.minimum-size.x-central-euro
       12
       font.minimum-size.x-cyrillic
       12
       font.minimum-size.x-devanagari
       12
       font.minimum-size.x-ethi
       12
       font.minimum-size.x-geor
       12
       font.minimum-size.x-gujr
       12
       font.minimum-size.x-guru
       12
       font.minimum-size.x-khmr
       12
       font.minimum-size.x-knda
       12
       font.minimum-size.x-mlym
       12
       font.minimum-size.x-orya
       12
       font.minimum-size.x-sinh
       12
       font.minimum-size.x-tamil
       12
       font.minimum-size.x-telu
       12
       font.minimum-size.x-tibt
       12
       font.minimum-size.x-unicode
       12
       font.minimum-size.x-user-def
       12
       font.minimum-size.x-western
       12
       font.minimum-size.zh-CN
       12
       font.minimum-size.zh-HK
       12
       font.minimum-size.zh-TW
       12
       gfx.blacklist.direct2d
       3
       gfx.blacklist.layers.direct3d9
       3
       gfx.blacklist.webgl.msaa
       4
       network.cookie.prefsMigrated
       true
       places.database.lastMaintenance
       1367011227
       places.history.expiration.transient_current_max_pages
       104858
       plugin.disable_full_page_plugin_for_types
       application/pdf
       privacy.donottrackheader.enabled
       true
       privacy.sanitize.migrateFx3Prefs
       true
 Graphics
       Device ID
       0x6740
       GPU Accelerated Windows
       1/1 OpenGL
       Vendor ID
       0x1002
       WebGL Renderer
       ATI Technologies Inc. -- ATI Radeon HD 6770M OpenGL Engine
       AzureCanvasBackend
       quartz
       AzureContentBackend
       none
       AzureFallbackCanvasBackend
       none
 JavaScript
       Incremental GC
       true
 Accessibility
       Activated
       false
       Prevent Accessibility
       0
 Library Versions
       Expected minimum version
       Version in use
       NSPR
       4.9.5
       4.9.5
       NSS
       3.14.3.0 Basic ECC
       3.14.3.0 Basic ECC
       NSSSMIME
       3.14.3.0 Basic ECC
       3.14.3.0 Basic ECC
       NSSSSL
       3.14.3.0 Basic ECC
       3.14.3.0 Basic ECC
       NSSUTIL
       3.14.3.0
       3.14.3.0
Site Moderator

Re: Version 20, Memory Leak Still?

yes, this all looks fairly normal to me - nothing that should give concerns in relation to RAM leaks. could you test if you can replicate the problem while you're in safemdoe (as explained by cor-el above) nevertehless, since it might provide some other clues... (hardware acceleration, jit-compiling and other things are turned off there)