perfview
perfview copied to clipboard
PerfView is a CPU and memory performance-analysis tool
The minimal rundown keyword should be `ForceEndRundown` instead of a non-existent keyword. This is required in order to support gathering the runtime version events from .NET Core. .NET Core no...
Fixes #1711 This brings the URL escaping in line with [this implementation](https://github.com/dotnet/sourcelink/blob/16ba25a5b808ab4794d8eeb945a836b32f2efc15/src/SourceLink.Tools/SourceLinkMap.cs#L214) from dotnet.
While investigating [this issue](https://github.com/OmniSharp/omnisharp-vscode/issues/5290) with the Microsoft C# Extension, we inspected other implementations of Source Link to see if they were subject to the same issue. By inspection we can...
Provides more complete heap dumps without sampling. For very large dumps, this can result in a more sluggish UI, but the benefit of the complete data outweighs the UI sluggishness....
When doing processing in batch/bulk, it would be more advantageous to allow the user to pass a `System.IO.Stream` into `new ETWTraceEventSource()` vs having to download the file to disk and...
``` perfcollect collect sample-threadtime -collectsec 10 -threadtime Collection started. Collection will automatically stop in 10 second(s). Press CTRL+C to stop early. ...STOPPED. Starting post-processing. This may take some time. Generating...
``` # perfcollect collect sample-pid-threadtime -collectsec 10 -threadtime -pid 1 Collection started. Collection will automatically stop in 10 second(s). Press CTRL+C to stop early. ...STOPPED. Starting post-processing. This may take...
EventPipe captured thread adjustment event with reason 8:  According to this document, there are listed reasons from 0x00 to 0x07: https://docs.microsoft.com/en-us/dotnet/framework/performance/thread-pool-etw-events#threadpoolworkerthreadadjustmentadjustment **Do we know what does 0x08 means?** I...
This results in higher working set, but also blocks the user from deleting the directory containing the symbols even after processing.
PerfView 3.0.4 uses for x64 dumps the 32 bit HeapDump which cannot work. Seems to be a regression issue. Please fix.