Segmentation fault when fetching graphics processes about nvml-wrapper HOT 6 CLOSED

Yeah, I actually hit this as well a few days ago on Windows 11 with the NVIDIA driver (not at my computer right now to check the version but I imagine it's the same). I also narrowed the segfault down to the same line. Like you say, I've never heard of this happening before and the wrapper code there hasn't changed. It seems to be a new thing caused by the NVIDIA driver update.

I noticed that this was happening immediately after I updated my driver and before I restarted my PC. After restarting the segfault went away. I wonder if the NVIDIA driver got in some sort of weird state after the update?

Have you restarted your machine after the driver update? Or can you consistently reproduce this even after restarting?

from nvml-wrapper.

It's been consistently happening, across multiple driver updates as well

from nvml-wrapper.

Gotcha. When I get a chance I'll dig in here and see what I can figure out.

If you find out anything more let me know 🙂.

from nvml-wrapper.

FWIW I spent some time looking into this again just now and I cannot reproduce the segfault. I also can't see any way that the wrapper is misusing the API as it's defined/documented.

Are you still running into this?

from nvml-wrapper.

Nope, seems to just work, though I wonder if that's the driver's fault or you making use of some undefined behavior when copying process info.

I just had a read over nvmlDeviceGetGraphicsRunningProcesses_v3 documentation and couldn't see anything obvious, though I guess we can't debug it anymore anyway because we can't reproduce it.

from nvml-wrapper.

Interesting. I'll keep an eye out.

from nvml-wrapper.