Featured Articles

IHS teardown reveals Galaxy S5 BOM

IHS teardown reveals Galaxy S5 BOM

Research firm IHS got hold of Samsung’s new flagship smartphone and took it apart to the last bolt to figure out…

More...
Galaxy S5, HTC One M8 available selling well

Galaxy S5, HTC One M8 available selling well

Samsung’s Galaxy S5 has finally gone on sale and it can be yours for €699, which is quite a lot of…

More...
Intel lists Haswell refresh parts

Intel lists Haswell refresh parts

Intel has added a load of Haswell refresh parts to its official price list and there really aren’t any surprises to…

More...
Respawn confirms Titanfall DLC for May

Respawn confirms Titanfall DLC for May

During his appearance at PAX East panel and confirmed on Twitter, Titanfall developer Respawn confirmed that the first DLC pack for…

More...
KFA2 GTX 780 Ti Hall Of Fame reviewed

KFA2 GTX 780 Ti Hall Of Fame reviewed

KFA2 gained a lot of overclocking experience with the GTX 780 Hall of Fame (HOF), which we had a chance to…

More...
Frontpage Slideshow | Copyright © 2006-2010 orks, a business unit of Nuevvo Webware Ltd.
Monday, 11 July 2011 14:41

Cut down version of Firefox out

Written by Nick Farell
firefox

Times they are a changing
As the Mozilla Foundation starts rolling out builds for testing in the Aurora channel one of them has caught our eye. Firefox 7 is still a long way off,  but some of the builds show that finally Mozilla is getting around to reducing the browser's memory footprint.

It seems that developers want to cut memory usage decrease by 30 percent in the latest Aurora builds. These improvements seem to have come out of the Mozilla's MemShrink project.  These have been focused on plugging memory leaks and improving garbage collection.

Already in this built memory consumption was down and the browser felt a bit snappier than previous versions.
he Aurora and Beta versions are available for download from Mozilla's website.


Nick Farell

E-mail: This e-mail address is being protected from spambots. You need JavaScript enabled to view it
blog comments powered by Disqus

Comments  

 
+4 #1 Stewox 2011-07-11 15:30
ive looked into memdump of firefox several times, there is SAME information being repeated 3 times ...


everything is saved , whatever you type, whatever you click , ... it's all there, just extensions like LAZARDus keep it up to save your text if you lose it by clicking into anoher site

Firefox does that kind of thing but ONLY sometimes some sites do no support firefox well and do not recover text when you hit backward button. And firefox doesn't have functionality behind that only via backward button.

There's one base, then it's the second copy, THEN it's the "X_Y_Z" copy (with underscores between each letter) , and then the extension copy , ... so a lot of stuff is repeated many times in memory. Freaking hog
 
 
-7 #2 Stewox 2011-07-11 15:35
We don't need a cut down version , it's not the problem in it's functionality. it's a problem in DISFUNCTINALITY , bad code , and memory leaks, as wall as bad cleaning.
 
 
+18 #3 TechHog 2011-07-11 16:28
Another misleading title.
 
 
-2 #4 Nintendork 2011-07-11 17:04
It's not possible that after closing tabs and leaving just 1 in blank memory consumption doesn´t decrease. It remains at 250MB!!!


30% of that is not a solution. Firefox is broken.
 
 
+9 #5 The_Countess 2011-07-11 17:13
Quoting Nintendork:
It's not possible that after closing tabs and leaving just 1 in blank memory consumption doesn´t decrease. It remains at 250MB!!!


30% of that is not a solution. Firefox is broken.

actually that's nothing but a small garbage collection issue. its likely that if another program needs that memory, its released already.
 
 
+4 #6 dicobalt 2011-07-11 20:43
7? Pshaw! The nightly is at version 8.
 
 
+1 #7 Cartman 2011-07-12 06:35
lol how much RAM do you have 512 mb??

The fook you all complaining half of you have 8 gb of ram if not more...
 
 
+3 #8 Dribble 2011-07-12 09:15
Quoting Nintendork:
It's not possible that after closing tabs and leaving just 1 in blank memory consumption doesn´t decrease. It remains at 250MB!!!


30% of that is not a solution. Firefox is broken.


Depends on your memory management scheme - what's probably happening is there is little bits of memory still in use all over that 250mb. This means that while gaps are still re-usable by firefox they can't be properly freed for access by another programme.
 

To be able to post comments please log-in with Disqus

 

Facebook activity

Latest Commented Articles

Recent Comments