Comment #9 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
I am convinced that this is working as intended. V8 heap size tells how much memory it asked OS to commit (a peak possible consumption in a sense). V8 used heap size tells how much memory contains actually allocated objects. As far as I see both numbers are correct, it just mismatches a number that is counts something else entirely. If number of oranges mismatches number of apples it does not mean that we should start counting oranges in a different way.
Setting SIGSEGV is not an option. First of all it conflicts with Breakpad (which afaik installs its own handler) and its an additional layer of complexity that solves a nonexistent problem.
-- v8-dev mailing list [email protected] http://groups.google.com/group/v8-dev
