Exception EventPipe conversion

[quisitive-crogers]

Trying to consume the nettrace in PerfView results in an exception while converting to ETLX file.

Started: Opening trace.nettrace Creating ETLX file C:\Users\chris\AppData\Local\Temp\PerfView\trace_2e914def.etlx from C:\Users\chris\Documents\trace.nettrace Error: Exception EventPipe conversion: System.ArgumentOutOfRangeException: Valid values are between 0 and 999, inclusive. Parameter name: millisecond at System.DateTime..ctor(Int32 year, Int32 month, Int32 day, Int32 hour, Int32 minute, Int32 second, Int32 millisecond, DateTimeKind kind) at Microsoft.Diagnostics.Tracing.EventPipeEventSource.FromStream(Deserializer deserializer) at FastSerialization.Deserializer.ReadObjectDefinition(Tags tag, StreamLabel objectLabel) at FastSerialization.Deserializer.GetEntryObject() at Microsoft.Diagnostics.Tracing.EventPipeEventSource..ctor(PinnedStreamReader streamReader, String name) at Microsoft.Diagnostics.Tracing.Etlx.TraceLog.CreateFromEventPipeDataFile(String filePath, String etlxFilePath, TraceLogOptions options) at PerfView.EventPipePerfViewData.GetTraceLog(TextWriter log, Action3 onLostEvents)
[Error: exception while opening EventPipe data.]
Completed: Opening trace.nettrace (Elapsed Time: 0.122 sec)`

The application environment is a Linux container running on an Azure App Service. Steps taken to create and retrieve the trace are:

1. SSH into already running app service executing a standard web api.
2. export PATH="$PATH:/root/.dotnet/tools"
3. dotnet-trace collect -p
4. Do some tests via Postman
5. End trace
6. Ftp trace.nettrace to remote server for pickup
7. Download trace.nettrace from remote server.
8. Try to open file
   trace.zip

Target Framework is netcoreapp3.1
Linux image is based on mcr.microsoft.com/dotnet/core/sdk:3.1

[cheenamalhotra]

I'm facing this error in macOS, when capturing traces using dotnet trace targeting a .NET 9 Runtime process, and trying to open the nettrace file on Windows Perfview instance.

[brianrob]

Looking further at this issue - this should be fixed in the runtime and not in the parser. The parser is doing the right thing and failing when a value is out of range.

Filed dotnet/runtime#123103.