d6daf8b0af
FixedArrays hanging off recursively of the constant pool without any real objects in between can be considered as meta data. They are shared with optimized code (embedder pointers). Bug: v8:7266 Change-Id: I4006675e17e8eea3bdc8565254d80e2ffece0ad0 Reviewed-on: https://chromium-review.googlesource.com/883361 Reviewed-by: Ulan Degenbaev <ulan@chromium.org> Commit-Queue: Michael Lippautz <mlippautz@chromium.org> Cr-Commit-Position: refs/heads/master@{#50837} |
||
---|---|---|
.. | ||
categories.js | ||
details-selection.html | ||
details-selection.js | ||
global-timeline.html | ||
global-timeline.js | ||
histogram-viewer.html | ||
histogram-viewer.js | ||
index.html | ||
README.md | ||
trace-file-reader.html | ||
trace-file-reader.js |
Heap Stats
Heap stats is a HTML-based tool for visualizing V8-internal object statistics. For example, the tool can be used to visualize how much heap memory is used for maintaining internal state versus actually allocated by the user.
The tool consumes log files produced by d8 (or Chromium) by passing
--trace-gc-object-stats
or a trace captured using Chrome's tracing
infrastructure. Chrome trace files can either be processed as gzip or raw text
files.
Hosting requires a web server, e.g.:
cd tools/heap-stats
python -m SimpleHTTPServer 8000