You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 3, 2019. It is now read-only.
When opening this file with chrome://tracing (gunzip it first! see issue #4633) or the opening the result of trace2html I receive the error message in the title.
The event in question "Event76 176" starts at timestamp 87196094949 and ends at 87196119345 which is a higher value.
There are two unfinished events in the trace, "Event34 1929" and "Event34 1930". Deleting them doesn't eliminate the error.
Deleting the end entry of "Event76 176" also does not eliminate the error, which is strange because the error message is now complaining about an end time that doesn't even exist.
Deleting both start and end entries of "Event76 176" will eliminate the error and the file opens properly. However there is nothing unusual that I can see about this event. Here are the relevant lines:
I've seen similar open issues but they all seem to blame unfinished events ("B" without "E"). This looks like a different case.
https://drive.google.com/open?id=1IY9X-AbPlX8kflek87SOpj0K5BDTheuP
When opening this file with chrome://tracing (gunzip it first! see issue #4633) or the opening the result of trace2html I receive the error message in the title.
{"ph":"B","pid":"process4770 (system-wide)","tid":"0","ts":87196094949,"name":"Event76 176","args":{"timestamp-B":"Jan 14 04:11:02.105"}},
{"ph":"E","pid":"process4770 (system-wide)","tid":"0","ts":87196119345,"name":"Event76 176","args":{"timestamp-E":"Jan 14 04:11:02.129"}},
The text was updated successfully, but these errors were encountered: