DevTools: fix mixed arguments in Tracing.bufferUsage event

DevTools: fix mixed arguments in Tracing.bufferUsage event

Originally regressed by https://codereview.chromium.org/2500093002

BUG=b/36176396

Review-Url: https://codereview.chromium.org/2752083002
Cr-Commit-Position: refs/heads/master@{#457227}
Committed: https://chromium.googlesource.com/chromium/src/+/c8dc5d159a4716659d8698b093794f7c9eaa24ed

[caseq, 2017-03-15 19:38:01]

caseq@chromium.org changed reviewers:
+ dgozman@chromium.org

[dgozman, 2017-03-15 20:50:55]

lgtm

Why all the tests pass?

[caseq, 2017-03-15 20:53:15]

On 2017/03/15 20:50:55, dgozman wrote:

> 
> Why all the tests pass?

Well, these are hard to test for because of non-deterministic nature of data
there.

[caseq, 2017-03-15 20:53:17]

The CQ bit was checked by caseq@chromium.org

[commit-bot: I haz the power, 2017-03-15 20:54:03]

CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[commit-bot: I haz the power, 2017-03-15 22:04:53]

CQ is committing da patch.

Bot data: {"patchset_id": 1, "attempt_start_ts": 1489611197853360, "parent_rev":
"4b691bacf99e200dabfd140716f03fe91585ac7f", "commit_rev":
"c8dc5d159a4716659d8698b093794f7c9eaa24ed"}

[commit-bot: I haz the power, 2017-03-15 22:06:22]

Description was changed from

==========
DevTools: fix mixed arguments in Tracing.bufferUsage event

Originally regressed by https://codereview.chromium.org/2500093002

BUG=b/36176396
==========

to

==========
DevTools: fix mixed arguments in Tracing.bufferUsage event

Originally regressed by https://codereview.chromium.org/2500093002

BUG=b/36176396

Review-Url: https://codereview.chromium.org/2752083002
Cr-Commit-Position: refs/heads/master@{#457227}
Committed:
https://chromium.googlesource.com/chromium/src/+/c8dc5d159a4716659d8698b09379...
==========

[commit-bot: I haz the power, 2017-03-15 22:06:25]

Committed patchset #1 (id:1) as
https://chromium.googlesource.com/chromium/src/+/c8dc5d159a4716659d8698b09379...

[Nico, 2017-03-26 01:31:08]

A revert of this CL (patchset #1 id:1) has been created in
https://codereview.chromium.org/2776043002/ by thakis@chromium.org.

The reason for reverting is: Speculative, looks like this broke a bunch of
devtool tests on msan, first failure at
https://build.chromium.org/p/chromium.memory.full/builders/Linux%20MSan%20Tes...
but still broken 80 builds later..

[caseq, 2017-03-26 23:06:55]

On 2017/03/26 01:31:08, Nico wrote:
> A revert of this CL (patchset #1 id:1) has been created in
> https://codereview.chromium.org/2776043002/ by mailto:thakis@chromium.org.
> 
> The reason for reverting is: Speculative, looks like this broke a bunch of
> devtool tests on msan, first failure at
>
https://build.chromium.org/p/chromium.memory.full/builders/Linux%20MSan%20Tes...
> but still broken 80 builds later..

I'm sure this isn't the cause - these tests don't even use tracing, and the
stacks don't seem to have anything to do with the change. I would suspect
https://chromium.googlesource.com/chromium/src/+/2d7d2c3632187e2cfaaa5c6ec26d...
based on the stacks.