[tracing] Fix memory overhead accounting of TraceBufferVector
commit954f418961681edbaeb354d59c078b304a863a03
authorprimiano <primiano@chromium.org>
Tue, 7 Jul 2015 16:59:17 +0000 (7 09:59 -0700)
committerCommit bot <commit-bot@chromium.org>
Tue, 7 Jul 2015 17:01:04 +0000 (7 17:01 +0000)
treed4df04b918d6228b3e18f42c86b3528cb0b17867
parenta2b674bd81533aaf6970e84976edeb44a5cb46f8
[tracing] Fix memory overhead accounting of TraceBufferVector

When tracing estimates the memory overhead of its own structs
TraceBufferVector (which itself is just a vector of pointers)
doesn't take into account its own capacity.
This causes sub-accounting when using the "as much as possible"
record strategy, which causes a big upfront reservation.

BUG=495628

Review URL: https://codereview.chromium.org/1226933002

Cr-Commit-Position: refs/heads/master@{#337624}
base/trace_event/trace_event_impl.cc