Unable to read .nettrace file collected by dotnet-trace
Los mantenedores suelen responder en 1 día
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 4/5
- Tiempo estimado
- 3-5 días
- Aptitud para principiantes
- 35/100
- Tipo de issue
- Error
- Claridad
- Necesita aclaración
- Estado de actividad
- Estancado
- Área
- devtools
Línea de trabajo
Reproduce el problema con el comando documentado de dotnet-trace collect y, a continuación, intenta abrir el archivo .nettrace resultante en PerfView y Visual Studio mientras revisas los errores de EventPipe y FastSerialization que reportan. Se considera terminado cuando se haya identificado por qué se rechaza este archivo generado y se haya confirmado que el trace recopilado se abre correctamente en las herramientas afectadas.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
Description
Collected data using command
dotnet-trace collect --process-id **** --duration 00:00:00:30 --providers Microsoft-DotNETCore-SampleProfiler
But the result .nettrace file was not readable by either Visual Studio nor PerfView.
Visual Studio Log:
CreateEditorInstance
StreamJsonRpc.RemoteInvocationException: Not a understood file format: C:\Users\****\Downloads\w3wp.exe_20250919_140901.nettrace
at StreamJsonRpc.JsonRpc.<InvokeCoreAsync>d__156`1.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.DiagnosticsHub.NetTraceDocumentConverter.<ConvertFromAsync>d__10.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.DiagnosticsHub.DocumentsService.<OpenAsConvertedAsync>d__24.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at Microsoft.DiagnosticsHub.DocumentsService.<OpenAsConvertedAsync>d__24.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at Microsoft.DiagnosticsHub.DocumentsService.<OpenAsConvertedAsync>d__24.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.DiagnosticsHub.VisualStudio.Shell.Views.NetTraceEditorFactory.<>c__DisplayClass6_0.<<CreateEditorInstance>b__1>d.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.VisualStudio.Threading.JoinableTask.CompleteOnCurrentThread()
at Microsoft.VisualStudio.Shell.VsTaskLibraryHelper.Run(JoinableTaskFactory joinableTaskFactory, String waitCaption, Func`3 asyncMethod, Nullable`1 delayToShowDialog)
at Microsoft.DiagnosticsHub.VisualStudio.Shell.Views.NetTraceEditorFactory.<>c__DisplayClass6_0.<<CreateEditorInstance>b__0>d.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.VisualStudio.Shell.VsTaskLibraryHelper.<>c.<<FileAndForget>b__36_0>d.MoveNext()
RPC server exception:
FastSerialization.SerializationException: Not a understood file format: C:\Users\****\Downloads\w3wp.exe_20250919_140901.nettrace
at FastSerialization.Deserializer.Initialize(IStreamReader reader, String streamName)
at FastSerialization.Deserializer..ctor(IStreamReader reader, String streamName)
at Microsoft.Diagnostics.Tracing.EventPipeEventSource.<>c__DisplayClass2_0.<.ctor>b__0()
at Microsoft.Diagnostics.Tracing.EventPipeEventSource..ctor(PinnedStreamReader streamReader, String name, Boolean isStreaming)
at Microsoft.Diagnostics.Tracing.EventPipeEventSource..ctor(String fileName)
at Microsoft.Diagnostics.Tracing.Etlx.TraceLog.CreateFromEventPipeDataFile(String filePath, String etlxFilePath, TraceLogOptions options)
at Microsoft.DiagnosticsHub.DataWarehouse.ServiceModule.Controllers.DataWarehouseTraceEventServiceController.ConvertAsync(Guid sessionId, ConvertDocumentPayload convertDocumentPayload, List`1 analyzerPayloads, CancellationToken cancellationToken)
PerfView Log:
Started with command line: PerfView.exe w3wp.exe_20250919_140901.nettrace /ContinueOnError
PerfView Version: 3.1.24 BuildDate: Wed, 27 Aug 2025 11:35:13 GMT
PerfView Start Time 9/19/2025 2:20:41 PM
Started: View
Warning: PdbScope not found at **\Downloads\PerfViewExtensions\PdbScope.exe
Disabling the Image Size Menu Item.
Warning: ILSize not found at **\Downloads\PerfViewExtensions\ILSize.dll
Disabling the IL Size Menu Item.
Completed: View (Elapsed Time: 0.098 sec)
Started: Opening w3wp.exe_20250919_140901.nettrace
Creating ETLX file **\AppData\Local\Temp\PerfView\w3wp.exe_20250919_140901_cdf8e802.etlx from **\Downloads\w3wp.exe_20250919_140901.nettrace
Error: Exception EventPipe conversion: System.FormatException: Invalid FastSerialization header
at Microsoft.Diagnostics.Tracing.FastSerializationObjectParser.ValidateFastSerializationHeader()
at Microsoft.Diagnostics.Tracing.EventPipeEventSource.ParseHeaders()
at Microsoft.Diagnostics.Tracing.EventPipeEventSource..ctor(Stream stream, Boolean isStreaming)
at Microsoft.Diagnostics.Tracing.Etlx.TraceLog.CreateFromEventPipeDataFile(String filePath, String etlxFilePath, TraceLogOptions options)
at PerfView.EventPipePerfViewData.GetTraceLog(TextWriter log, Action`3 onLostEvents)
[Error: exception while opening EventPipe data.]
Completed: Opening w3wp.exe_20250919_140901.nettrace (Elapsed Time: 0.123 sec)
Configuration
dotnet-trace Windows x64 version 9.0.12.21003 downloaded from https://aka.ms/dotnet-trace/win-x64
Perfview version is 3.1.19
Visual Studio 2022 Community version is 17.0.36407.19
Data collected on Windows Server 2022 x64 version 10.0.20348
Server is running IIS version 10.0
.net core runtime installed on server is 8.0.4
- Lenguaje dominante
- C++
- Estrellas
- 1.3k
- Forks
- 407
- Merge medio
- 21 h 5 min
- PR fusionados (30 d)
- 78
Preparar el entorno
Inicia el contenedor de desarrollo del proyecto en tu navegador, con tu propia cuenta de GitHub.
- Sin Dockerfile ni archivo de Docker Compose
- Sin plantilla de pull request
- Sin guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de dotnet/diagnostics
-
Fix StackAndOtherTests.script line number verification for .NET 11 and Windows x64Quizá libre de nuevo Un pull request para esta issue se cerró sin fusionarse. Abierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 65/100
dotnet/diagnostics#5884 · 2 comentarios ·
Los mantenedores suelen responder en 1 día
-
Dificultad 4/5 3-5 días Aptitud para principiantes 25/100
dotnet/diagnostics#6225 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 4/5 3-5 días Aptitud para principiantes 48/100
dotnet/diagnostics#6213 ·
Los mantenedores suelen responder en 1 día
-
Isolate SOS hosting from other debugger extensions that use managed codePosiblemente ocupada Un pull request vinculado a esta issue está abierto o ya se fusionó. Abiertobug
Dificultad 5/5 Más de una semana Aptitud para principiantes 25/100
dotnet/diagnostics#6207 ·
Los mantenedores suelen responder en 1 día
-
Known Build Error
Dificultad 4/5 3-5 días Aptitud para principiantes 49/100
dotnet/diagnostics#6190 ·
Los mantenedores suelen responder en 1 día
Todos los issues de dotnet/diagnostics
Issues similares
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 76/100
AutoHotkey/AutoHotkey#380 ·
-
documentation
Dificultad 1/5 1-3 horas Aptitud para principiantes 84/100
Los mantenedores suelen responder en 1 día
-
Lua File: add readWhole()Abierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 69/100
grumpycoders/pcsx-redux#2667 ·
-
GCC 15.2: -Wcast-qual warning - cast discards const qualifier from pointer target type (H5trace.c)Abierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 73/100
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 88/100
google/tensorstore#305 ·