Comment #1 on issue 28620 by [email protected]: Private virtual memory in "about:memory" is different from process explorer http://code.google.com/p/chromium/issues/detail?id=28620
This is something memory TF is actively looking at but I could not find a bug filed. --------------- (v8/virtual alloc + tcmalloc) vs process explorer discrepancy Some functions (CreateDIB? something like this) accounts for allocation/commit that was not previously accounted for Happens a lot on sites with heavy graphics use Need to track size of committed bytes by OS, not just tcmalloc/v8 -- some of these may be allocated and committed by the kernel. Not being leaked, but not tracked in our current methods, leading to the discrepancy Should be less hidden allocations by the OS on Linux, will check back after we understand Windows better. --------------- -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings -- Automated mail from issue updates at http://crbug.com/ Subscription options: http://groups.google.com/group/chromium-bugs
