Comment #12 on issue 2191 by [email protected]: V8 reports heap memory size bigger than process private memory
http://code.google.com/p/v8/issues/detail?id=2191
If you are interested in memory consumption you should look at used bytes (confusingly called "live" in the column) not heap size. We can even reorder these numbers inside the column to put an emphasis on the right thing: used matters --- heap size matters less.
And once again: V8 does not report amount of virtual address space it just reserves. Otherwise it would be _way_ higher. It reports amount of memory it asked OS to commit. It is true that OS can be lazy in performing actual commit, but that is something beyond V8's reach and actually is not important to V8 at all as for V8 purposes this memory looks like successfully committed and can be used for allocation .
Would you prefer V8 to workaround OSes lazyness by touching every page inside the region it commits to make numbers of apples and oranges agree? I can hardly see any reason in that.
-- v8-dev mailing list [email protected] http://groups.google.com/group/v8-dev
