RangeError: Invalid array length
    at CpuUsageAuditor.computeCpuUsageSeries_ (chrome://tracing/tracing.js:4301:224)
    at CpuUsageAuditor.runAnnotate (chrome://tracing/tracing.js:4299:54)
    at auditors.forEach (chrome://tracing/tracing.js:1188:312)
    at Array.forEach (<anonymous>)
    at addImportStage (chrome://tracing/tracing.js:1188:284)
    at Task.run (chrome://tracing/tracing.js:2172:104)
    at runAnother (chrome://tracing/tracing.js:2178:566)
    at runTask (chrome://tracing/tracing.js:2151:57)
    at processIdleWork (chrome://tracing/tracing.js:2156:116)
    at window.requestIdleCallback.timeout (chrome://tracing/tracing.js:2149:81)

This error occurs if the startTime event doesn't make it into the trace. This can happen if the target thread is unresponsive during the trace. We're able to get samples for that trace but the startTime event doesn't always get put in the trace. These traces right now just about and if the trace is collected with chrome://tracing the trace is thrown out.

If you have a ProfileChunk event:
        {
            "args": {
                "data": {
                   ...
                    ]
                }
            },
            "cat": "filer",
            "id": "0xb0ba8fa0b1b3dd98",
            "name": "ProfileChu",
            "ph": "P",
            "pid": 88445,
            "tid": 39815,
            "ts": 273569870279,
            "tts": 8652
        },

The missing event that fixes the trace that is sometimes missing:
        {
            "args": {
                "data": {
                    "startTime": 273569650744
                }
            },
            "cat": "disabled-by-default-v8.cpu_profiler",
            "id": "0xb0b2e3c864e0ae0c",
            "name": "Profile",
            "ph": "P",
            "pid": 86305,
            "tid": 775,
            "ts": 273569650746,
            "tts": 1550221
        },