Bot releases are hidden (Show)
Published by brianrob about 5 years ago
Roll-up until 8/7/2019.
Published by brianrob over 5 years ago
Roll-up until 7/1/2019.
Published by brianrob over 5 years ago
Roll-up until 7/1/2019.
Published by brianrob over 5 years ago
Roll-up until 6/18/2019.
Includes support for the new EventPipe nettrace format.
Published by brianrob over 5 years ago
Roll-up until 6/18/2019.
Published by brianrob over 5 years ago
Rollup until 5/6/2019.
Published by brianrob over 5 years ago
Rollup until 5/6/2019.
Published by brianrob over 5 years ago
Rollup until 4/24/2019.
Includes preview support for streaming from EventPipe.
Published by vancem over 5 years ago
Rollup until 4/1/2019
Published by vancem over 5 years ago
This is mostly a bug fix release from the 2.0.26. However there are a few small new features:
To get the tool simply download the PerfView.exe executable and use it. I include the PDB files in case you need to debug something, but that is a rare case and you don't need to do that normally.
The PerfView64.exe is optional. It is a small wrapper that launches PerfView as a 64 bit application. If you are dealing with very large traces that cause 'out of memory' errors, this can be used to avoid the problem. Note that you need PerfView.exe to be present next to PerfView64.exe for it to work.
Like all versions of PerfView you can see the specific release notes from the past year by accessing the 'Help -> Release Notes' menu entry.
You can also see detailed informational about what changes went into this release by viewing the Github history.
Published by vancem over 5 years ago
Rollup until 3/20/19
Published by vancem over 5 years ago
Rollup until 2/20/19.
Published by vancem almost 6 years ago
Rollup until 1/18/.19. This includes support for Microsoft.Diagnostics.Tracing.Stacks.Formats.SpeedScopeWriter. See #842 for more.
Published by vancem almost 6 years ago
Rollup until 1/2/19. This includes support for generic Microsoft-Diagnostics-ActivityTracking. See https://github.com/Microsoft/perfview/pull/828.
Published by vancem almost 6 years ago
Rollup until 12/13/18. This includes a fix for CoreFX bug associated with decoding nullable types in EventSources. https://github.com/dotnet/corefx/issues/33013 Publishing this so that bug can be fixed.
Published by vancem almost 6 years ago
Rollup until 12/12/2018. Bug that provoked the release was https://github.com/Microsoft/perfview/issues/755, where Building with TraceEvent on a Desktop framework would sometimes give a missing dependency error for the Microsoft.Win32.Registry.dll.
Published by vancem almost 6 years ago
Fixed a moderately serious bug introduced int 2.0.29, that causes confusion about the thread for an event. The ramifications might be widespread but subtle. We noticed it in the 'Thread Time with Tasks' views. We recommend upgrading from 2.0.29 ASAP.
Published by vancem about 6 years ago
This is a bug fix release from the 2.0.23. If you use the Thread Time View with Start-Stop Tasks view you will want to pick up this new release as there was a regression in May that caused AWAIT time to not be displayed. Otherwise there are only small fixes.
To get the tool simply download the PerfView.exe executable and use it. I include the PDB files in case you need to debug something, but that is a rare case and you don't need to do that normally.
The PerfView64.exe is optional. It is a small wrapper that launches PerfView as a 64 bit application. If you are dealing with very large traces that cause 'out of memory' errors, this can be used to avoid the problem. Note that you need PerfView.exe to be present next to PerfView64.exe for it to work.
Like all versions of PerfView you can see the specific release notes from the past year by accessing the 'Help -> Release Notes' menu entry.
You can also see detailed informational about what changes went into this release by viewing the Github history.
Published by vancem about 6 years ago
This is a minor bug fix from the previous release. The Start-Stop activity logic had disabled showing AWAIT time. If you use that view, then this bug fix is important, otherwise it is not.
Published by vancem about 6 years ago