Unable to read .nettrace file collected by dotnet-trace
I maintainer di solito rispondono entro 1 giorno
Nessuno ha ancora preso questa issue.
Valutazione
- Difficoltà
- 4/5
- Tempo stimato
- 3-5 giorni
- Idoneità per principianti
- 35/100
- Tipo di issue
- Bug
- Chiarezza
- Da chiarire
- Stato di attività
- Ferma
- Ambito
- devtools
Direzione di ricerca
Riproduci il problema con il comando documentato dotnet-trace collect, quindi prova ad aprire il file .nettrace risultante in PerfView e Visual Studio esaminando al contempo gli errori EventPipe e FastSerialization segnalati. Il lavoro è completato quando avrai identificato perché questo file generato viene rifiutato e confermato che la traccia raccolta si apre correttamente negli strumenti interessati.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Descrizione
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
- Lingua principale
- C++
- Stelle
- 1.3k
- Fork
- 407
- Merge medio
- 21h 5m
- PR unite (30g)
- 78
Preparare l'ambiente
Avvia il container di sviluppo del progetto nel browser, con il tuo account GitHub.
- Nessun Dockerfile né file Docker Compose
- Nessun modello di pull request
- Nessuna guida per i contributori
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Altre issue di dotnet/diagnostics
-
Fix StackAndOtherTests.script line number verification for .NET 11 and Windows x64Forse di nuovo libera Una pull request per questa issue è stata chiusa senza essere unita. Aperta
Difficoltà 2/5 1-3 ore Idoneità per principianti 65/100
dotnet/diagnostics#5884 · 2 commenti ·
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 4/5 3-5 giorni Idoneità per principianti 25/100
dotnet/diagnostics#6225 ·
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 4/5 3-5 giorni Idoneità per principianti 48/100
dotnet/diagnostics#6213 ·
I maintainer di solito rispondono entro 1 giorno
-
Isolate SOS hosting from other debugger extensions that use managed codeForse già presa Una pull request collegata a questa issue è aperta o già unita. Apertabug
Difficoltà 5/5 Più di una settimana Idoneità per principianti 25/100
dotnet/diagnostics#6207 ·
I maintainer di solito rispondono entro 1 giorno
-
Known Build Error
Difficoltà 4/5 3-5 giorni Idoneità per principianti 49/100
dotnet/diagnostics#6190 ·
I maintainer di solito rispondono entro 1 giorno
Tutte le issue di dotnet/diagnostics
Issue simili
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 76/100
AutoHotkey/AutoHotkey#380 ·
-
documentation
Difficoltà 1/5 1-3 ore Idoneità per principianti 84/100
I maintainer di solito rispondono entro 1 giorno
-
Lua File: add readWhole()Aperta
Difficoltà 2/5 1-3 ore Idoneità per principianti 69/100
grumpycoders/pcsx-redux#2667 ·
-
GCC 15.2: -Wcast-qual warning - cast discards const qualifier from pointer target type (H5trace.c)Aperta
Difficoltà 2/5 1-3 ore Idoneità per principianti 73/100
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 88/100
google/tensorstore#305 ·