Getting an error when giving bigrig a file

[ErisDS]

I'm having a go at creating a trace and sending it to bigrig for the first time, and I've run into a problem I don't understand.

What I did:

• Installed bigrig globally @ 1.2.0
• In Chrome 48.0.2564.97 (64-bit)
• I opened the app I want to test (localhost)
• I closed every other tab
• I opened the dev tools, went to the timeline tab, hit cmd+r and waited for the timeline to be recorded
• Right click Save Timeline Data, saved it to my desktop
• Ran bigrig --file ~/Desktop/Timeline.json -s -pp

Here's the output:

Hannahs-MacBook-Air ~/Desktop $ bigrig --file ~/Desktop/Timeline4.json -s -pp

/usr/local/lib/node_modules/bigrig/lib/third_party/tracing/base/iteration_helpers.js:303
    for (var value of map.values())
                   ^^
Usage: bigrig <input> [<option>]

Options:
  --file, -f            The trace file to be parsed              [default: ""]
  --pretty-print, --pp  Pretty print the results              [default: false]
  --strict, -s          Throw if extensions are found         [default: false]

I also tried creating the trace in an incognito tab, but that resulted in a zero-byte trace file.

Any ideas what I'm doing wrong?

[paullewis]

I wonder if there's been a trace file change recently. It's something of a cat-and-mouse game to keep the trace parser inline with the traces that Chrome generates. Is there any way you can post the file up so I can repro the issue at my end? I'll try taking tip-of-tree for the tracing parser and see if that fixes things.

[ErisDS]

Here ya go http://puu.sh/mNcOz.json

[paullewis]

Ahhhhhhh wondering if it's something to do with node versions! for(var x of y) is ES2015 stuff, which is, like, Node 4+, isn't it? Dangit, that's my bad for failing to update the engines property in the package.json. In the short term I've updated the minimum version in package.json, but I'll grab a copy of 0.12 and see if the fixes would be straight forward.

[ErisDS]

Oh yeah, I'm totally set to 0.10.x by default 😁