New issue
Advanced search Search tips

Issue 594231 link

Starred by 2 users

Issue metadata

Status: WontFix
Owner: ----
Closed: May 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 2
Type: ----



Sign in to add a comment

chrome://tracing can't load huge traces

Project Member Reported by dskiba@chromium.org, Mar 11 2016

Issue description

Here is 300+ MiB trace: https://drive.google.com/file/d/0B_Hmi138MnbJZnllMWNUY2FDRU0/view?usp=sharing

There are issues with loading this file in chrome://tracing:

1. When opened as is (as .gz archive) the following error box is displayed after a while:

While importing:
RangeError: Invalid string length
    at Array.join (native)
    at Object.f [as string] (chrome://tracing/tracing.js:2806:20803)
    at Object.c.transformTo (chrome://tracing/tracing.js:2806:22556)
    at Object.c.transformTo (chrome://tracing/tracing.js:2806:6723)
    at Function.GzipImporter.inflateGzipData_ (chrome://tracing/tracing.js:3616:114)
    at Object.GzipImporter.extractSubtraces (chrome://tracing/tracing.js:3616:360)
    at Object.createImports (chrome://tracing/tracing.js:435:112)
    at Object.Task.run (chrome://tracing/tracing.js:732:13)
    at runAnother (chrome://tracing/tracing.js:744:136)
    at runTask (chrome://tracing/tracing.js:707:57)

OK, so we failed to inflate. This takes us to the next point.

2. When extracted and loaded as a huge .json file, UI just flashes nothing happens. There is no error, no "Aw, Snap", nothing.


I think we should at least show some useful error, and at best, we should just load the trace. 300 MiB is not so bad.
 

Comment 1 by dskiba@chromium.org, Mar 11 2016

Cc: primiano@chromium.org
Components: Internals>Tracing
Components: Speed>Tracing
Components: -Internals>Tracing

Comment 5 by dskiba@chromium.org, May 16 2018

Status: WontFix (was: Untriaged)
One goal of Perfetto is to fix this exact issue.

Sign in to add a comment