Comment #2 on issue 21041 by erik.corry: Linux: Renderer using 23GB of virtual memory, 6GB of resident memory http://code.google.com/p/chromium/issues/detail?id=21041
The /proc/xxx/maps file that is attached is pretty strange. I'm not sure there's a V8 active in there at all. Here is a characteristic sequence you would find in the maps file if V8 were active: 7fe3781c0000-7fe379000000 rwxp 7fe3781c0000 00:00 0 7fe379000000-7fe379100000 rw-p 7fe379000000 00:00 0 7fe379100000-7fe379800000 ---p 7fe379100000 00:00 0 7fe379800000-7fe379900000 rw-p 7fe379800000 00:00 0 7fe379900000-7fe37a000000 ---p 7fe379900000 00:00 0 7fe37a000000-7fe37a1c0000 rw-p 7fe37a000000 00:00 0 There's a big chunk from 81c0000 to 11c0000. The first part is the code heap (rwxp). Then you see part 1 of new space, rw-p, starting on a very aligned address. Then there is space reserved for new space to grow into. After that, the 2nd part of new space, the second reserved space for new space to grow into and then the data heap (rw-p). I don't see that pattern in the maps file attached. I notice that this is a 64 bit Chromium build. Has this phenomenon been seen on a 32 bit build. -- 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 -~----------~----~----~----~------~----~------~--~---
