I recently added changes for the test runner to add tracing data for what test are running. When trying to load the data into the trace viewer I get:

Uncaught (in promise) Error: The trace is too long or the CPU usage counter interval is too small, leading to too many CPU usage intervals.
    at HTMLDivElement.computeCpuUsage_ (tracing.js:4194)
    at HTMLDivElement.initialize (tracing.js:4193)
    at HTMLDivElement.appendCpuUsageTrack_ (tracing.js:4386)
    at HTMLDivElement.updateContentsForLowerMode_ (tracing.js:4376)
    at HTMLDivElement.updateContents_ (tracing.js:4373)
    at HTMLDivElement.set model [as model] (tracing.js:4370)
    at HTMLElement.set model [as model] (tracing.js:4421)
    at HTMLElement.set model [as model] (tracing.js:4591)
    at HTMLElement.<anonymous> (tracing.js:4607)

Which I have narrowed down to the individual trace event having too long of a duration.

Example broken data:

[{"category": "process_argv", "name": "process_argv", "args": {"argv": ["Unimportant"]}, "pid": 28335, "ts": 267962068732.43402, "tid": 140153717864256, "ph": "M"}
,

{"category": "python", "name": "system_health.common_mobile", "args": {}, "pid": 23794, "ts": 1649581131.6239998, "tid": 140574615140096, "ph": "B"},
{"category": "python", "name": "system_health.common_mobile", "args": {}, "pid": 23794, "ts": 4419189562.359, "tid": 140574615140096, "ph": "E"}



If I change the second ts to be 1719189562.359 it works as expected.