[android] Nettrace collected on CoreCLR Android including JIT+Loader events won't display in Perfview Loader/JITStats views.

Open
#114,216 5 comments 0 reactions 1 assignee View on GitHub

@lateralusX is already working on this.

Since Apr 3, 2025.

Assessment

This issue has not been assessed yet.

Description

area-Diagnostics-coreclr os-android

Collecting JIT and Loader data through EventPipe on Android CoreCLR works and include all expected information, but there seem to be some parsing error in Perfviews Runtime Loader and JITStats views. The following error occurs in perfviews log:

Started: Opening dotnet-dsrouter_20250402_152420.nettrace
ETL Size 2.627 MB ETLX Size 2.668 MB
Completed: Opening dotnet-dsrouter_20250402_152420.nettrace (Elapsed Time: 0.056 sec)
Started: Opening JITStats
Completed: Opening JITStats (Elapsed Time: 0.098 sec)
Exception Occurred: System.IndexOutOfRangeException: Index was outside the bounds of the array.
at Microsoft.Diagnostics.Tracing.Analysis.TraceLoadedDotNetRuntime.<>c__DisplayClass32_0.b__16(GCMarkWithTypeTraceData data)
at Microsoft.Diagnostics.Tracing.TraceEventDispatcher.DoDispatch(TraceEvent anEvent)
at Microsoft.Diagnostics.Tracing.Etlx.TraceLogEventSource.Process()
at PerfView.PerfViewJitStats.WriteHtmlBody(TraceLog dataFile, TextWriter output, String fileName, TextWriter log)
at PerfView.PerfViewHtmlReport.GenerateReportFile(StatusBar worker, TraceLog trace)
at PerfView.PerfViewHtmlReport.<>c__DisplayClass17_1.b__0()
at PerfView.StatusBar.<>c__DisplayClass22_0.b__0()
An exceptional condition occurred, see log for details.
Started: Opening EventStats
Completed: Opening EventStats (Elapsed Time: 0.054 sec)
Started: Opening myport.sock_20250402_144917.nettrace
ETL Size 0.295 MB ETLX Size 0.125 MB
Completed: Opening myport.sock_20250402_144917.nettrace (Elapsed Time: 0.045 sec)
Started: Opening EventStats
Completed: Opening EventStats (Elapsed Time: 0.000 sec)

Appears to be some issue with GC MarkWithType data events and might not be unique to Android, an OSX trace including the same GC event will also trigger this error.

Dominant language
C#
Stars
18.3k
Forks
5.6k
PR merge metrics
PR metrics pending

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from dotnet/runtime

All issues in dotnet/runtime

Similar issues

More C# issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.