Each Chrome process has many threads and each thread has one or two stacks (two stacks for 32-bit Chrome on a 64-bit OS) and the net effect of this on memory and address space consumption is difficult to see. Modifying tools\win\IdleWakeups to summarize this information would be fairly simple and could reveal interesting patterns.