There, memory usage registered just shy of 400 MB.
FIREFOX OS X MEMORY LEAK MAC OS X
We tried the same thing on a MacBook Air running Mac OS X Lion 10.7.1 with a 1.4 GHz Intel Core 2 Duo and 2 GB of RAM, with better results on Firefox 6.0.2. Just a few hours after opening a Firefox browser (with version 6.0.2), with seven tabs open running web sites including the self-refreshing Drudge Report, AOL.com’s main portal, Google Plus, Google Docs, Youtube, the New York Post’s web site, CRN.com and a local TV news web site, the combined memory usage by Firefox and one of its plug-ins ran in excess of 1 GB on a PC built with an Intel Quad Core Q6600 at 2.40 GHz, with 4 GB of RAM and running Windows 7 Professional 64 bit. We wanted to get a look at some of these issues for ourselves, and it wasn’t very difficult to re-create the results. Mozilla developers, responding to the reports, repeated standard statements about memory issues often being the result of specific web sites used, third-party software and browser extensions.
In all, more than 100 Mozilla users had reported having memory issues in recent weeks, including more than half that number in the last week. Some who posted on the Mozilla support board reported memory leaks expanding to eat more than 1 GB after a couple of hours of use, while others said it occurred very quickly after boot-up.
FIREFOX OS X MEMORY LEAK INSTALL
Some memory leaks have been tied to browser plug-ins, while other users insist they are doing nothing exotic to cause such significant memory use.įor example, wrote one user: “Firefox 6.0.2 + Safe Mode on a clean Win7 64 install (Q6600 processor+6 (GB) Ram) AND IT STILL REACHES 1.5 (GB) of RAM.” In a number of issues posted on Mozilla’s support message board over the past several weeks, users report repeated instances of Firefox eating more than 1 GB of memory during basic tasks. Three and a half years after developers plugged “hundreds” of memory leaks in the Firefox browser that had slowed many PCs to a halt, memory leaks in Firefox 6.0.2 are apparently once again frustrating users.
0 kommentar(er)
