Hmm seems some recent regression. Various report came also in 
https://github.com/catapult-project/catapult/issues/2328

The issue here is the ungzipped trace being > 256M.
The question is why. Looking.

Ok looks like that trace has 88 processes and the produced json is 800 MB, way beyond our limit of 256 M.
Supporting large traces will be addressed as part of Tracing V2.
In the meantime I hacked up a script to strip down a trace and keep only the last two memory dumps, guaranteeing that all processes are preserved.

Script here, should beautify and check in catapult somewhere soon (bug stays assigned to me for this).

https://gist.github.com/primiano/2c429e8ba993c26264e66800f46fca0f

I agree we won't be able to do much until Tracing V2 lands. Thanks for writing the script. When you want to check the file in, please add the following two files:


tracing/tracing_build/SCRIPT_NAME.py <-- your script
tracing/bin/SCRIPT_NAME              <-- a short Python file with a __main__ method that calls your script

Example: https://github.com/catapult-project/catapult/blob/2befef4332bccf830c80b0c1806ad44409bb1b9c/tracing/tracing_build/merge_traces.py and https://github.com/catapult-project/catapult/blob/2befef4332bccf830c80b0c1806ad44409bb1b9c/tracing/bin/merge_traces.

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/6b16de9d3ef1b121411cfc63954408b51b28d945

commit 6b16de9d3ef1b121411cfc63954408b51b28d945
Author: catapult-deps-roller <catapult-deps-roller@chromium.org>
Date: Wed Jul 27 13:32:44 2016

Roll src/third_party/catapult/ 48b4f78a2..3ea537c50 (2 commits).

https://chromium.googlesource.com/external/github.com/catapult-project/catapult.git/+log/48b4f78a2919..3ea537c50254

$ git log 48b4f78a2..3ea537c50 --date=short --no-merges --format='%ad %ae %s'

BUG= 630965 

TBR=catapult-sheriff@chromium.org

Review-Url: https://codereview.chromium.org/2189613002
Cr-Commit-Position: refs/heads/master@{#408111}

[modify] https://crrev.com/6b16de9d3ef1b121411cfc63954408b51b28d945/DEPS

I checked in tracing/bin/strip_memory_infra_trace to short-term solve situations like this.
CLosing this bug, the real fix will come with Tracing V2