Linked by Thom Holwerda on Tue 20th Nov 2007 16:54 UTC, submitted by lefty78312
Permalink for comment 285539
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
News
Linked by Thom Holwerda on 06/18/13 22:33 UTC
Linked by Anonymous on 06/18/13 22:26 UTC
Linked by Thom Holwerda on 06/18/13 22:25 UTC
Linked by Thom Holwerda on 06/18/13 17:45 UTC
Linked by Thom Holwerda on 06/18/13 17:32 UTC, submitted by poundsmack
Linked by Thom Holwerda on 06/17/13 17:58 UTC
Linked by Thom Holwerda on 06/17/13 17:52 UTC
Linked by Thom Holwerda on 06/14/13 21:03 UTC
Linked by Thom Holwerda on 06/14/13 20:46 UTC
Linked by Thom Holwerda on 06/14/13 17:32 UTC
More News »
Sponsored Links



Member since:
2007-03-20
If you haven't seen this blog entry, its worth reading. A great description (illustrated!) of why Firefox ends up hogging so much memory-- fairly bad heap fragmentation, and what they are now doing about it.
Great blog comments too, really nice to see dtrace and other analysis tools to benchmark and debug Mozilla. Plenty of useful solutions offered, and the blogger is currently testing OpenBSD's malloc with positive results.
http://blog.pavlov.net/2007/11/10/memory-fragmentation/