chrome:tracing fails when the trace is too large |
|||||||||
Issue description(Parallel Catapult bug: https://github.com/catapult-project/catapult/issues/2826) The underlying issue here is that, in Javascript, we gunzip the innerHTML of a <script> tag. However, because Javascript strings are limited to ~268 million characters, this causes trace viewer to blow up for long traces, which can pretty easily exceed 268MB given the current storage format (JSON). Please follow the Catapult bug for the most up-to-date discussion on this.
,
Jan 10 2017
,
Jan 10 2017
I have started to work on a fix for this; it should be ready for review by the end of this week.
,
Jan 30 2017
Issue 681839 has been merged into this issue.
,
Feb 10 2017
,
Feb 10 2017
,
Mar 27 2017
,
Apr 5 2017
,
Aug 11 2017
https://github.com/catapult-project/catapult/issues/2826 is fixed. Closing. |
|||||||||
►
Sign in to add a comment |
|||||||||
Comment 1 by charliea@chromium.org
, Jan 10 2017