Firefox memory usage and memory leak news

Many Mozilla community members, including both volunteers and Mozilla Corporation employees, have been helping to reduce Firefox's memory usage and fix memory leak bugs lately. Hopefully, the result of this effort will be that Firefox 3 uses less memory than Firefox 2 did, especially after it has been used for several hours.

Memory usage

Federico Mena-Quintero submitted a patch to make Firefox discard decompressed image data after five seconds (bug 296818). ImageLib module owner Stuart Parmenter experimented with a competing idea in bug 386377, but now he plans to help with Federico's patch. The patch will make image data join text runs in using time-based caching rather than traditional space-bounded caching.

Aaron suggested having an "about:memory" page showing a breakdown of Firefox's memory use (bug 392351). When I pointed out the bug to Brendan Eich, he excitedly assigned the bug to himself.

Eli Friedman discovered that nsFloatCache was no longer necessary and eliminated most of it (bug 381385).

Memory leaks

David Baron checked in a patch for the last bug that contributed to RLk on Linux, bringing the number of XPCOM objects leaked during this test to zero. Since this test runs on Tinderbox, it's likely that regressions will be noticed quickly, even if they don't turn Tinderbox orange.

Robert Sayre created a script to load random pages and see whether they cause leaks. The random URLs come from the Yahoo directory (biased toward older, top-level pages), del.icio.us (biased toward newer, geeky pages), and AltaVista (biased toward pornography). The script detects leaks using trace-refcnt, the same test used by RL; future versions might use trace-malloc in order to catch additional leaks. Robert has caught at least 6 distinct leak bugs using this script, 3 of which have already been fixed. See LeakingPages and bug 394517 for details.

David Baron created a series of patches to the cycle collector to aid in debugging leaks. With this code, DEBUG_CC builds of Firefox can notice when an object "expected to be garbage" is not collected and then explain in detail why it was not collected.

Steve England tested the top 500 web sites, finding two leaks. Later, he tested the top 20 Firefox extensions and found leaks in several of them.

David Baron recorded seven leak debugging screencasts, which you can watch to see how David Baron debugs real leaks.

Kris Zyp found a leak in the JavaScript Engine when using the watch method (bug 394709). Igor Bukanov responded quickly with not only a patch for the bug but also a leak detection patch to enable regression testing of JavaScript Engine leaks. I asked him to modify his patch so I could use jsfunfuzz to test for JavaScript Engine leaks, and he did. (This led me to find several bugs in evalcx, but no additional leaks.)

David Baron got the stack walking code and the stack fixer working on Mac, making it possible to use trace-malloc and the refcount balancer on Mac (bug 336517, bug 392118).

How to help

You don't have to be a C++ programmer to help find leaks in Firefox.

If you're a Firefox user, an easy way to help is to browse with a trunk nightly build wrapped in a script that calls leak-gauge.pl when Firefox exits. If it reports that documents or windows leaked, try to figure out how to reproduce the leak and then file a bug report.

If you're an advanced user, you can do something similar with with trace-refcnt, which detects leaks of all reference-counted objects, not just windows and documents. Build Firefox with the .mozconfig option "--enable-logrefcnt" (or build debug) and run your build with XPCOM_MEM_LEAK_LOG=2. When Firefox exits, it will print a detailed but understandable summary of what types of objects leaked.

If you're are a C++ programmer and want to help diagnose or fix bugs, check out Performance:Leak_Tools along with David Baron's screencasts, and hang out in #developers on irc.mozilla.org.

83 Responses to “Firefox memory usage and memory leak news”

  1. FP Says:

    Whenever I see complaints (mainly in Digg comments) about Fx memory usage there seem to be two types:
    1. Why is Fx using 80MB when browser-Y only uses 70MB?
    2. Why is Fx using 300MB/500MB/1GB/etc on my system?

    Is there any consensus as to what causes the second type and whether these fixes will help?

  2. Andy Burns Says:

    I’m looking forward to seeing the results of this work, it’ll be much appreciated if it gets firefox back to where it used to be with regard to consuming memory.

    Could I suggest a test of a 10 minute session of scrolling and zooming around in google maps hybrid mode as something guaranteed to to eat over 1GB of memory?

  3. Firefox Memory Problems Fixed? « FVTer Moving and Being Says:

    […] Problems Fixed? September 20, 2007 Posted by fvter in Programming, Technology. trackback News on the MozillaBlog would seem to suggest that Firefox may finally fix some of its memory issues: […]

  4. warpozio Says:

    If you’re a Firefox user, an easy way to help is to browse with a trunk nightly build wrapped in a script that calls leak_gauge.pl when Firefox exits. If it reports that documents or windows leaked, try to figure out how to reproduce the leak and then file a bug report.

    Sounds easy, but how would I do this? Is there a site describing step-by-step how to launch this pl script?

  5. Arthur Says:

    Could I suggest a test of a 10 minute session of scrolling and zooming around in google maps hybrid mode as something guaranteed to to eat over 1GB of memory?

    I think that’s one of the problems with those memory consumption bugs, they seem to be dependent on too many external circumstances to be triggered. I’ve just did what you asked for (on my old Athlon xp with 512 MB of RAM) and memory usage didn’t go up much at all. Which means developers have a hard time fixing the bugs if they can’t consistently reproduce them.

    If you’re a Firefox user, an easy way to help is to browse with a trunk nightly build wrapped in a script that calls leak_gauge.pl when Firefox exits. If it reports that documents or windows leaked, try to figure out how to reproduce the leak and then file a bug report.

    Sounds easy, but how would I do this? Is there a site describing step-by-step how to launch this pl script?

    I’ve just wrapped it in the following few lines:

    export NSPR_LOG_MODULES=DOMLeak:5,DocumentLeak:5,nsDocShellLeak:5
    export NSPR_LOG_FILE=nspr_leaks.log
    firefox/firefox
    perl leak-gauge.pl nspr_leaks.log

    Should work on any *nix system with a bash/sh shell and perl installed.

  6. Andy Burns Says:

    that’s one of the problems with those memory consumption bugs, they seem to be dependent on too many external circumstances to be triggered

    I understand the problem, it does occur consistently for me and hence is a noticeable annoyance with FF, but if it’s triggered by other factors will be difficult to trackdown.

  7. Ian Says:

    (cross posted on the extensions leak post)

    A while back I suggested that Mozdev add the ‘mlk’ keyword for memory leak bugs. There are currently 11 open ones labelled as such, some of which definitely still leak after all this time (e.g. Sage):

    https://www.mozdev.org/bugs/buglist.cgi?keywords=mlk

    It would be great if Mozilla could help out with these leaks in some situations.

  8. Afinando Firefox « TIDDER Says:

    […] estge post se apuntan los pasos que se están dando para acabar de una vez por todas con el problema de gestión de […]

  9. Kim Sullivan Says:

    I hope that the image related bug https://bugzilla.mozilla.org/show_bug.cgi?id=213391 (FF disregarding memory limits) will finally also get some love, after bug 296818 gets fixed :-D

  10. Nÿco Says:

    When right-clicking in a webpage, then “Information on the page”, you’ll have a tabbed dialog box. The first tab (“General”) has got a “Size” item, could you add a “Size in memory” item?

  11. mat Says:

    about:memory will be great.
    I wish somebody would add automatic unloading of plugin when not used
    (ie for example, if I close all pages then flash, java,… should be unloaded…)

  12. Gérard Talbot Says:

    Jesse,

    In your “How to help” section, you did not mention D. Baron’s memory leak monitor extension
    https://addons.mozilla.org/firefox/addon/2490
    which IMHO has proven useful to detect memory leakages in add-on extensions:

    https://www.mozdev.org/bugs/show_bug.cgi?id=14013

    https://www.mozdev.org/bugs/show_bug.cgi?id=16409

    Regards,

    Gérard Talbot

  13. David Baron Says:

    It’s worth noting that the cycle collector debugging patches only do anything in a build where DEBUG_CC is defined. (A debug build alone isn’t sufficient.)

  14. Jesse Ruderman Says:

    It’s worth noting that the cycle collector debugging patches only do anything in a build where DEBUG_CC is defined. (A debug build alone isn’t sufficient.)

    Good point. I changed the wording in the post to make it less confusing.

  15. Cameron Says:

    It’s great to get updates on this kind of stuff – thanks very much :D

  16. tester Says:

    so should that perl script work on Mac OS X as well?

    which trunk build to get then? or any one will do?

  17. Jesse Ruderman Says:

    I know leak-gauge.pl works on Mac, and Arthur’s sh wrapper looks like it should work on Mac too.

    Since we’re fixing leaks fairly frequently, I recommend getting the most recent trunk nightly build.

  18. Jesse Ruderman Says:

    I know leak-gauge.pl works on Mac. Arthur’s sh wrapper looks like it should work on Mac too.

    Since leak bugs are fixed fairly frequently, I recommend getting the most recent trunk nightly build. If it’s too unstable, drop back to Alpha 8, I guess.

  19. Gary Says:

    Hey Jesse, that perl script will show that something leaks if extensions are disabled and then firefox restarted.

    ===
    Leaked inner window 15d19a90 (outer 1be88d0) at address 15d19a90.
    … with URI “chrome://browser/content/hiddenWindow.xul”.
    Leaked outer window 1be88d0 at address 1be88d0.
    Summary:
    Leaked 2 out of 2 DOM Windows
    Leaked 0 out of 1 documents
    Leaked 0 out of 1 docshells
    ===

    that’s when I disabled the DOM inspector and Talkback, then quit FF and re-run the commands.

    Is this an expected behaviour?

  20. Jesse Ruderman Says:

    Kinda. EM-restart tends to confuse whatever launched Firefox, since it looks like Firefox exited. It’s not a big deal if there’s a leak in EM-restart, since the process exited early anyway.

  21. Joakim Says:

    you really cant compare FF to IE.

    half of IE’s memory usage is not in iexplore.exe, but explorer.exe.

  22. Support this story on Stirrdup Says:

    Firefox memory usage and memory leak news…

    This story has been submitted to Stirrdup. Your support can help it become hot….

  23. Cartel Says:

    I didn’t know that.
    We can make Firefox better.

  24. polarizer Says:

    FF’s memory consumption teases me too often. Nice to see that i can help to figure out where depends on. Thx for the profiler script link.

    my 2 cents – the polarizer

  25. Pavan Gayakwad Says:

    I am not using firefox from past 8 months because of its memory leakage issue. It would be really great is FF team fixes and optimizes it as much as possible. Anyways, I am waiting for FF3 with lots of expectations specially in the matter of ‘speed’.

  26. John S Says:

    maybe if they get this one fixed they can tackle Thunderbird as well. ive had a case where Thunderbird, sitting idle was suing 135mb ram. i maximize it then minimize it to try again and it goes to like 1mb then it climbs up again to about 40-50mb.

    thats the only real reason holding me back from using Thunderbird 100% of the time.

  27. dirk Says:

    Well, the MEMORY problem is only a part of the story imho.
    It`s the CPU HOG problem which requires me to kill and restart firefox.
    ~40 tabs in total distributed over three windows run smoothly for hours, even days. then, all of a sudden, firefox is consuming ~98% cputime.
    Strange. And nasty.

  28. Firefox 3 Memory Leaks Status Update - CyberNet News Says:

    […] have memory leaks, and now Mozilla’s very own Jesse Ruderman has brought up a similar issue in regards to Firefox 3’s performance. Jesse said that both Mozilla employees and volunteers have been working tirelessly to fix the […]

  29. Mike Says:

    Use http://mr.himki.net/OpenBSD_malloc_Linux.c

  30. Firefox 3 memory usage | meyithi.com Says:

    […] Jesse Ruderman » Firefox memory usage and memory leak news Many Mozilla community members, including both volunteers and Mozilla Corporation employees, have been helping to reduce Firefox’s memory usage and fix memory leak bugs lately. Hopefully, the result of this effort will be that Firefox 3 uses less memory than Firefox 2 did, especially after it has been used for several hours. […]

  31. Frank 2 Says:

    Have any of you ever run Gimpel Lint (or similar) on Firefox? While it can be overwhelming at first (I got something like 250k warnings on our 600k lines of code the first time), it can find _VERY_ subtle bugs, and major problems.

  32. Synthesis2k2 Says:

    If you guys are looking for sites to go to that use a large amount of memory, go to YouTube and open a few videos in different tabs. Even two videos, left open for a number of hours, takes memory usage up a good number of megs.

    -Syn

  33. Robert H. Goretsky Says:

    Taking a quick look at the perl script to trace memory leaks, it looks like it will run in XP too.. Is this correct? Robert H. Goretsky of Hoboken, NJ

  34. Cometstars Says:

    Great! I hope it fixes up sites that leak memory like this chat one.

  35. dreesemonkey . com » Blog Archive » Stuff for 9/21/2007 Says:

    […] Firefox 3 fixing some of the memory leak issues? […]

  36. Novedades sobre el uso de memoria de Firefox Says:

    […] tienes interés en seguir el desarrollo de Firefox, Jesse Ruderman publica las novedades sobre la mejora en la gestión de memoria que realiza el navega…. Escrito a las 19:28 | Envia esta nota por correo electrónico Por Alberto Verdoy | Lee más de: […]

  37. Cyde Weys Says:

    I’ve long thought that the complaints about Firefox memory usage were exaggerated, but I guess it turns out that some real problems do exist (though some have already been fixed in CVS, as it were). Keep up the good work in making Firefox as good as possible.

    I have to echo the suggestions above about opening lots of YouTube videos and scrolling around a lot in Google Maps to create sure-fire memory links. The only qualm I have is that the memory leaks caused by YouTube might be more of a Flash plugin issue than a Firefox issue. I know the Flash plugin causes Firefox to crash a lot on me under GNU/Linux, for example.

  38. foxiewire.com Says:

    Firefox memory usage and memory leak news…

    News about memory usage and memory leak of Firefox……

  39. meneame.net Says:

    Firefox 3 solventará los problemas con la fuga de memoria [eng]…

    Por todos es conocido el problema de fuga de memoria (memory leak) de Firefox. Pues bien, algunos miembros de la Fundación Mozilla y dos voluntarios han estado trabajado en ello. Gracias a ese esfuerzo Firefox 3 consumirá menos memoria que su predece…

  40. Max Says:

    Ah, at last! I actually started searching for alternatives to Firefox until they fixed this (but came up with nothing). I am happy to hear this (and so is my computer).


    Max … Out!
    http://www.cmyos.com – free online operating system

  41. Martin Cleaver Says:

    This has been a very slow process, as many of us were reporting these issues many moons ago back in 1.0… :(
    I do hope this will mean I can close the chapter on regularly restarting Firefox when I notice the computer has slowed to an almost halt.

  42. Second Life Loser » Help Find Memory Leaks in Firefox Says:

    […] usage and fix any memory leaks in the browser. If you’re not a programmer, Firefox programmer Jesse Ruderman says you can still help: “If you’re a Firefox user, an easy way to help is to browse with a […]

  43. Jesse Ruderman Says:

    This post made the Digg front page:

    http://digg.com/software/Firefox_memory_usage_and_memory_leak_news

  44. TheWebosphere : Firefox 3: Say Goodbye To Firefox’s Memory Leaks? - Consumer Web, Internet Tech, and Web 2.0 Startup News Says:

    […] god awful memory leaks might be a thing of the past once the third edition rolls around. Various people have been working hard at patching up what is commonly known as the browser’s biggest fault. […]

  45. » Help Find Memory Leaks in Firefox Tech Web Daily: Just another Tech News Blog Says:

    […] usage and fix any memory leaks in the browser. If you’re not a programmer, Firefox programmer Jesse Ruderman says you can still help: “If you’re a Firefox user, an easy way to help is to browse with a […]

  46. dude Says:

    Hope they make the UI as snappy as Opera, hope.

  47. Tu también puedes ayudar a FireFox Says:

    […] Si estás interesado, puedes ir al blog de Ruderman y consultar más información. […]

  48. Artemis3 Says:

    Be careful with plugins, they fall outside Firefox control. For example Flash and Adobe Reader love to cause high CPU usage and many times crash the browser.

  49. pd Says:

    If you’re a Firefox user, an easy way to help is to browse with a trunk nightly build wrapped in a script that calls leak-gauge.pl when Firefox exits.

    Hi Jesse, I’d like to help. Where can I get such a “nightly build wrapped in … leak-guage.pl”

  50. Clement Says:

    I would like to take part in this program but I would like to find out information on one issue. What is the effect of browsing with a trunk nightly build wrapped in a script, that calls leak-gauge.pl when Firefox exits, on browser speed

  51. Firefox 3 Firefox 2 ye göre daha az hafıza kullanacak. Says:

    […] Adresindeki habere göre firefox kullanan fakat aşırı hafıza tüketiminden şikayetçi olan (örneğin ben) kullanıcılar firefox 3 ün çıkmasıyla bu sorunundan kurtulacak.Yeni sürümün testleri hızla devam etmekte hazırlanan bir scriptle rastgele sayfalar ziyaret edilmekte ve hafıza taşması oluşturanlar ve buna sebep olan bug lar tespit edilmekte bu adrestetaşmaya neden olan sayfaları görebilir.Eğer sizde firefox un gelişimine yardım etmek istiyorsanız şu adresi ziyaret edip nasıl yapabileceğinizi öğrenebilirsiniz.. […]

  52. pd Says:

    More information. I’ve recently purchased a second box. Running nightlies on my main home computer is a PITA. Anyway this second box has Perl installed. All I’d like is a little step-by-step help and hopefully I can help solve the scourge that is FX memory issues.

  53. pd Says:

    Oh yeah, it’s a Windows XP box.

  54. Jesse Ruderman Says:

    pd, if you have Bash, you can use the script that Arthur pasted earlier. If you don’t, you should be able to make a similar DOS script (.bat file) using “set” instead of “export”. IIRC, with “set” you use a space instead of an equals sign.

    Clement, enabling the logging used by leak-gauge.pl should not slow down Firefox much, since it only logs information about certain “large” objects (windows, documents, docshells).

  55. Fozw - Noticias Web » Firefox 3 solventará los problemas con la fuga de memoria [eng] Says:

    […] » noticia original […]

  56. pd Says:

    Start, Run, notepad, Enter

    SET NSPR_LOG_MODULES DOMLeak:5,DocumentLeak:5,nsDocShellLeak:5
    SET NSPR_LOG_FILE nspr_leaks.log
    firefox/firefox
    perl leak-gauge.pl nspr_leaks.log

    Save As tstMemLeaks.bat

    C:\Perl>tstMemLeaks.bat

    C:\Perl>SET NSPR_LOG_MODULES DOMLeak:5,DocumentLeak:5,nsDocShellLeak:5
    Environment variable NSPR_LOG_MODULES not defined

    C:\Perl>SET NSPR_LOG_FILE nspr_leaks.log
    Environment variable NSPR_LOG_FILE not defined

    C:\Perl>firefox/firefox
    ‘firefox’ is not recognized as an internal or external command,
    operable program or batch file.

    C:\Perl>perl leak-gauge.pl nspr_leaks.log
    Can’t open perl script “leak-gauge.pl”: No such file or directory

  57. Jesse Ruderman Says:

    I was wrong about the “set” syntax; you do need the equals signs. If there’s a difference between the bash “export” syntax and the DOS “set” syntax it involves how they handle quotes and spaces.

    You’ll have to replace “firefox/firefox” with the path to your firefox.exe, of course. You can download leak-gauge.pl using the link in the post.

  58. pd Says:

    Woohooo it’s happening!

  59. Rez Says:

    Re http://wiki.mozilla.org/LeakingPages

    Dunno if this might be helpful, or give you somewhere else to look, but for what it’s worth:

    Some of these pages also trigger a Windows resource leakage bug that goes all the way back to core Mosaic code, so is seen in various builds of pre-Moz Netscape and IE as well.
    The principle trigger for that bug is visible active objects inside another structure, usually meaning either links with a lot of visible text or flash embeds, inside a table cell. I’m guessing CSS’s substitution for table cells has the same effect.
    In an offending page of yesteryear, I was able to get rid of the leak-effect simply by shortening the *visible* text in links that were inside table cells.

    The problem as described in Firefox sounds so similar, and is tickled by such similar pages, I can’t help thinking there’s some common factor here.

  60. Dag Wieers Says:

    I can only hope that the common memory leaks, that are straightforward to fix, are backported to the Firefox 1.5 and 2.0 series. This is important for Enterprise distributions where application upgrades are often not tolerated.

    I know that this is something that the Linux vendors can do, but it would make more sense if this effort was made under the Mozilla umbrella than done by individual vendors.

  61. asmith42 Says:

    pd, could you post your “working” version of the .bat file?
    Save some of us lazy people some time :)

    (Windows 2K and XP also have a more advanced shell:
    .bat -> command.com — legacy/compatability
    .cmd -> cmd.exe )

  62. Vlad Says:

    I still don’t understand why loading a 2 mb xml file in firefox needs to use 170 megs of ram.. I’m sure there can be more efficient algorthims to add +s and -ses to the tree.

  63. Bill Says:

    I am concerned about the next javascript engine, Tamarin using a conservative garbage collector (MMgc) instead of a precise one. It could have a lot of false positives with compressed image data and retain more memory.

  64. goarilla Says:

    (Windows 2K and XP also have a more advanced shell:
    .bat -> command.com — legacy/compatability
    .cmd -> cmd.exe )

    hahahahaha yeah right
    did you ever use the bash or tcsh shells?
    you stupid fool!

  65. DigitMemo.com » Firefox Working to Fix Memory Leaks Says:

    […] Mozilla community members, including both volunteers and Mozilla Corporation employees, have been helping to reduce Firefox’s memory usage and fix memory leak bugs […]

  66. Diaa Sami Says:

    This is greaaaat news, I think that performance(processing and memory usage) is the ONLY firefox drawback currently, with improved performance users will have no excuse for using other browsers.

  67. [News] Firefox Working to Fix Memory Leaks - Gamerz Needs - For All Your Gaming Needs! Says:

    […] Mozilla community members, including both volunteers and Mozilla Corporation employees, have been helping to reduce Firefox’s memory usage and fix memory leak bugs lately. Hopefully, the result of this effort will be that Firefox 3 uses […]

  68. Jesse Ruderman Says:

    This is on Slashdot, too: http://slashdot.org/article.pl?sid=07/09/24/1521240

  69. Planet Malaysia Says:

    My Ubuntu Feisty Firefox always crash when I open up few chat screen with meebo. Weird!

  70. Ravenent Says:

    “(Windows 2K and XP also have a more advanced shell:
    .bat -> command.com — legacy/compatability
    .cmd -> cmd.exe )”

    “hahahahaha yeah right
    did you ever use the bash or tcsh shells?
    you stupid fool!”

    Errm… How about Windows PowerShell?

  71. tecosystems » links for 2007-09-25 Says:

    […] Jesse Ruderman » Firefox memory usage and memory leak news good to see the Mozilla folks focusing on performance. Firefox has taken a nosedive for me in performance terms of late, though it seems probable that that’s extension related. (tags: mozilla firefox memoryleaks performance via:#redmonk) […]

  72. Jesper Says:

    Doesn’t some huge memory usages come from some leaky addons?

  73. Firefox Memory Leaks « PaQueSepas Says:

    […] bueno, al parecer ya lo están arreglando  Posted by Carlos Filed in Noticias, Tecnología Tags: Browsers, […]

  74. Ray Kiddy Says:

    You say that people could use a script. Like what script? Maybe like the script in https://bugzilla.mozilla.org/show_bug.cgi?id=390971….

    Well, it might need to get reviewed first.

  75. Gulsin 2.0rg - El hermano feo de tux » Firefox y el consumo de memoria Says:

    […] Vientos. […]

  76. Mozilla looking to plug memory leaks in Firefox Says:

    […] in Firefox 2.0) hasn’t gone unnoticed by the fine folks of the Mozilla community. In fact, they’ve been going memory leak crazy. That’s good news, especially for users of older Macs with older versions of the OS as Firefox […]

  77. » Firefox 3 consumirá menos recursos Says:

    […] notará cuando llevemos unas horas navegando con él. Además cualquiera puede contribuir enviando ciertos datos (inglés) sobre el comportamiento de su Firefox […]

  78. Firefox memory usage and memory leak new @ bloglsia Says:

    […] Desarrolladores de Firefox están trabajando para que la versión 3 del navegador consuma menos memoria. […]

  79. Firefox 3 consumirá menos memoria Says:

    […] SquareFree (vía […]

  80. Contribuiamo a Firefox3 GranParadiso! « Il blog di Sleeping Says:

    […] segnalare memory leak si può fare riferimento a questo blog. Per segnalare i memory leak, vi consiglio di installare l’estensione Leak Monitor che ha il […]

  81. Firefox 3 consumerà meno memoria « Fabry6210’s Weblog Says:

    […] i ranghi dei volontari che tra quelli degli impiegati della Corporation, stanno lavorando sodo per ridurre il consumo di memoria di Firefox e correggere i memory leak che hanno contraddistinto le incarnazioni più recenti della volpe di […]

  82. Browser Comparisons and Firefox Links - Firefox Facts Says:

    […] Firefox Memory Leak News […]

  83. On the mobile web, Firefox memory issues and more with Chris Hoffman : Mozilla Links Says:

    […] its success. For footprint and memory use in particular there is some great work that was recently announced and everyone should read about it at. I guess that was a pretty long winded answer to the memory […]