Linked by Thom Holwerda on Thu 13th Mar 2008 20:41 UTC, submitted by RJop
Mozilla & Gecko clones "While Firefox 2 used less memory than it's predecessor, Firefox 1.5, we intentionally restricted the number of changes to the Gecko platform (Gecko 1.8.1 was only slightly different than Gecko 1.8) on which Firefox was built. However, while the majority of people were working on Firefox 2/Gecko 1.8.1, others of us were already ripping into the platform that Firefox 3 was to be built on: Gecko 1.9. We've made more significant changes to the platform than I can count, including many to reduce our memory footprint. The result has been dramatic."
Thread beginning with comment 305007
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE: What concerns me more
by sorpigal on Fri 14th Mar 2008 14:12 UTC in reply to "What concerns me more"
sorpigal
Member since:
2005-11-02

I am not sure the X memory usage is a leak. I know X caches image data and I am not sure what the retention policy is. It's still a bug, IMO, but it may be by design.

Reply Parent Score: 2

RE[2]: What concerns me more
by siride on Fri 14th Mar 2008 14:58 in reply to "RE: What concerns me more"
siride Member since:
2006-01-02

No, it's a leak. I've used xrestop to compare what X thinks it has allocated and what cat /proc/`pgrep X`/smaps says it has in its heap. The differences are often astounding. I've had the X server have over 700MB allocated in its heap and xrestop claims that it only has, say, 20MB of resources allocated. It's ridiculous.

Reply Parent Score: 3

PlatformAgnostic Member since:
2006-01-02

Firefox might be causing heap fragmentation in X (you'd expect this if firefox were making tons of small pixmap allocations).

Reply Parent Score: 4