New issue
Advanced search Search tips

Issue 737786 link

Starred by 0 users
Status: Assigned
Owner:
primiano@chromium.org
Cc:
paulmiller@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug



Sign in to add a comment

merge_traces script produces unexpected output

Project Member Reported by paulmiller@chromium.org, Jun 28 2017 
Attached are:

trace_v9.json - a trace with 1 memory dumps
trace_v11.json - a trace with 2 memory dumps
trace_diff.json - the result of `merge_traces -o trace_diff.json trace_v*`

Maybe I'm using it wrong, but I'd expect trace_diff to have 3 memory dumps (those "M" buttons at the top), since that's how many were in the inputs. But it only has 2.
traces.tar.xz
109 KB Download

Comment 1 by dskiba@chromium.org, Jun 28 2017 

The resulting trace is a weird mix of data from both sources: it has 2 events with data from v11, but pids of browser process are different - they are taken from v9.

Comment 2 by dgozman@chromium.org, Sep 21 2017

Components: -Platform>DevTools>Tracing Speed>Tracing

Comment 3 by benhenry@chromium.org, Aug 1

Status: Assigned (was: Untriaged)
►

Sign in to add a comment