I’m on an rtx 2080 ti on driver 431.36 and I’m trying to profile my d3d12 application using the new GPU trace features.
Looks like there’s some trouble with present(), looking at the disassembly, it’s trying to dereference a null this pointer. I’ve already tried disabling the debug layer in the dx control panel, and that didn’t do anything.
here’s the callstack:
Exception thrown at 0x00007FFD94B130ED (nvwgf2umx.dll) in example.exe: 0xC0000005: Access violation reading location 0x0000000000000028.
I downloaded your attachment and deleted your post. feel free to PM me with it again if you would like a record of sending it. We can’t make attachments just for mods unfortunately. :(
I have a similar issue with GPU Trace. When I run my application with GPU Trace, it crashes with an “Access violation reading location …” exception on the first call to Present.
The frame debugger and frame profiler both seem to work, but GPU Trace does not.
There are (at least) 2 samples that can be used to reproduce the issue:
Samples\01-ClearScreen: This is a minimal sample that just clears the screen.
Samples\02-Cube: This sample just draws a cube.
In both of those samples, a message box should appear which allows the debugger to be attached to the running application started with GPU Trace.
I am unable to reproduce the crash using the Microsoft samples here (https://github.com/microsoft/DirectX-Graphics-Samples) but I can’t easily determine what I am doing different in my own application that causes the crash to occur.
I am using:
Nsight Graphics 2020.6.1.0 (build 29393650)
GPU: Titan RTX
Driver version: 460.89
Hello Jeremiah. So, the difference between the DX samples and yours is that you get the DXGIFactory back from the DXGIAdapter through GetParent to create your swapchain. We fail to handle that correctly - that’s a bug we need to fix. It will be done in a future version of GPU Trace. Meanwhile, you can keep a pointer to your DXGIFactory around within e.g. dx12lib::Adapter, and use that in SwapChain::SwapChain to create your swapchain. I did a quick hack to try that, and I could capture 02-Cube.
Hello,
Thank you for using Nsight Graphics and sorry you ran into this issue. We are investigating this issue and will let you know if we need any additional information from you.
Regards,