I converted a .nettrace file to the chromium format via dotnet-trace convert and noticed that my 15s long trace was only displayed as being 15ms long. After some digging and consulting the documentation, it appears that a timestamp expressed in milliseconds is being written into the ts field that expects a microsecond timestamp.
This bug has been previously reported here https://github.com/dotnet/diagnostics/issues/1315#issuecomment-653632216 but incorrectly classified as a bug in chromium. I believe this confusion might have been due to setting
writer.Write("\"displayTimeUnit\": \"ms\", ");
just a few lines below but alas this is only a display concern
I converted a .nettrace file to the chromium format via
This bug has been previously reported here https://github.com/dotnet/diagnostics/issues/1315#issuecomment-653632216 but incorrectly classified as a bug in chromium. I believe this confusion might have been due to setting
dotnet-trace convertand noticed that my 15s long trace was only displayed as being 15ms long. After some digging and consulting the documentation, it appears that a timestamp expressed in milliseconds is being written into thetsfield that expects a microsecond timestamp.just a few lines below but alas this is only a display concern