Fails on very large capture files

[Tridacnid]

We ran this on a large codebase and the final capture file was 3.8GB. After several seconds, the analyze phase fails with the output:

Analyzing build trace from './results'...
ERROR: JSON parse error expected end of input.
  no trace events found.

The ./results file appears to be intact. Running the tool on a smaller subset of our codebase worked just fine.

Thanks for the great project! It's already helping us immensely.

[Tridacnid]

Turns out there was an extra curly brace in one of our .json files from clang. Removing that and rerunning --stop and --analyze works great.