Chrome Version: 59.0.3054.0 dev
OS: ChromeOS Minnie

What steps will reproduce the problem?
(1) Record a trace with chrome://tracing.

What is the expected result?

Expect that it loads and is visualized.

What happens instead?

Error: No clock sync markers exist pairing clock domain "LINUX_FTRACE_GLOBAL" with target clock domain "LINUX_CLOCK_MONOTONIC".
    at ClockSyncManager.getTimeTransformerRaw_ (chrome://tracing/tracing.js:2095:410)
    at ClockSyncManager.getModelTimeTransformer (chrome://tracing/tracing.js:2095:13)
    at FTraceImporter.importEvents (chrome://tracing/tracing.js:4888:418)
    at importer (chrome://tracing/tracing.js:1150:232)
    at task.subTask (chrome://tracing/tracing.js:1146:262)
    at Task.run (chrome://tracing/tracing.js:2075:104)
    at runAnother (chrome://tracing/tracing.js:2082:267)
    at runTask (chrome://tracing/tracing.js:2056:57)
    at processIdleWork (chrome://tracing/tracing.js:2061:116)
    at window.requestIdleCallback.timeout (chrome://tracing/tracing.js:2054:81)