For more details, see this issue.

If you are running a Chromium-based browser, one workaround is to download your data as JSON and load it in your browser's viewer at "about://tracing". This run's data can be found here: