Re: Issue 243895 in chromium: Graph memory allocations over time in about:tracing

[chro...@googlecode.com]

Comment #1 on issue 243895 by jame...@chromium.org: Graph memory
allocations over time in about:tracing
http://code.google.com/p/chromium/issues/detail?id=243895

Maybe put the hierarchy into the left column of the trace list, then draw
the graphs inline in the trace view.

processTrack

ObjectSnapshotTrack (ObjectInstanceTrack, something like that)


--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings

[chro...@googlecode.com]

Updates:
Blockedon: chromium:255063

Comment #6 on issue 243895 by jame...@chromium.org: Graph memory

allocations over time in about:tracing
http://code.google.com/p/chromium/issues/detail?id=243895

Initial patch out for review at https://codereview.chromium.org/15418002/

There's a problem with the GPU sandbox that prevents us from profiling that
process. Getting a heap profile attempts to open /proc/self/maps, which is
intercepted by the security sandbox via a signal handler, which allocates
memory (it shouldn't), which causes a deadlock.

Issue 255063 relates to fixing the GPU sandbox.

[chro...@googlecode.com]

Comment #7 on issue 243895 by j...@google.com: Graph memory allocations

over time in about:tracing
http://code.google.com/p/chromium/issues/detail?id=243895

We'll fix that sandbox bug quickly, but meanwhile you can run with
--disable-gpu-sandbox for testing.