| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This version of memory_watcher can run under Vista, even though the
recursive calls that it handles are appearing often enough that there
is a performance penalty. With this landed, it may be possible for other
folks to run the tool, and I can work on improving its performance.
This CL also resolves the problem with hanging processes. Although
memory reporting can only be done once, and it leaves a pile of memory
"hanging around," the browser can be cleanly exited.
Tweaks include outputing the aggregate stacks such that the largest
stacks appear at the start of the output file.
This version avoids ongoing aggregation of stats in favor of only
doing the aggregation at dump-time. This probably enhances performance
at run-time, although it is hidden (on Vista) by the recursive calling.
This also simplifies the tracking code a fair amount.
There is some evidence that a small number of duplicate calls are being
made to "track" the same memory region, without an intervening free (i.e.,
call to "untrack"). The code to better diagnose this is currently in
place, but ifdef'ed, as it is only useful under a debugger. Exercise
of this code (turning a stack-frame list into a human readable stack
trace string) currently causes some corruption shortly after it triggers,
so I can't leave it on full time.
r=mbelshe
Review URL: http://codereview.chromium.org/366031
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@31299 0039d316-1c4b-4281-b951-d872f2087c98
|
