Linked by Thom Holwerda on Thu 27th Dec 2012 19:50 UTC
Permalink for comment 546513
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:
2005-09-14
It's not so much lying as it is being difficult to give an accurate representation of it. If the same shared library is loaded by multiple apps, it's actually only loaded into memory once and then mapped into each corresponding app's address space (at least the code section ; the data and other modifiable sections are mapped COW). That consequently makes it difficult to accurately assess the true memory usage of a given app, since, if the library is being used by more than one, you can't really lay the blame for that additional memory onto any given app, hence the complex and often confusing numbers one gets as far as memory usage goes.