Nsight Aftermath 2020.2
NVIDIA® Nsight™ Aftermath 2020.2.1 - Release Notes and Known IssuesNew Support:
- Added Nsight Aftermath support for Linux platforms
- You now have the ability to be able to generate GPU "mini-dumps" when a device lost event or GPU exception occurs on your Linux based applications.
- Added Nsight Aftermath support for the Ampere microarchitecture.
- Shader PDBs are now supported as a separate shader debug data source.
- Implemented minor bug fixes
- Aftermath is only supported on NVIDIA Pascal architecture GPUs and newer as the amount of information available for older GPU architectures is limited.
- The use of Aftermath D3D event markers or Vulkan diagnostic checkpoints introduces CPU overhead. To maintain good performance, limit usage to a reasonable amount.
- [D3D] The full Aftermath feature set is only supported for D3D12.
- [D3D] The experimental GFSDK_Aftermath_DX12_RegisterResource function causes a memory leak.
- [D3D] GFSDK_Aftermath_PageFaultInformation function sometimes returns an incorrect pAppResource pointer.
- [D3D] In certain situations, Aftermath event markers may not be reported on Pascal GPUs.
- [D3D] Shader debug information for legacy DXBC shaders is unsupported.
- [Vulkan] On Linux, due to a driver limitation the device status reported by `GFSDK_Aftermath_GpuCrashDump_GetDeviceInfo` is always `GFSDK_Aftermath_Device_Status_Unknown`. This will be fixed in an upcoming Linux display driver release.
- [Vulkan] On Linux, due to a driver limitation the channel being reported as reset by `GFSDK_Aftermath_GpuCrashDump_GetDeviceInfo` is always `3D` even if the crash happened on a compute queue. This will be fixed in an upcoming Linux display driver release.
For an overview of Nsight™ Aftermath and access to resources, please visit the main Nsight™ Aftermath page.
NVIDIA® Nsight™ Aftermath 2020.2 is available for download under the NVIDIA Registered Developer Program.
Note that documentation is included in this download.