When I try to profile a vulkan application, the application does launch without issue and the profiler does begin its process when the application shuts down but nsight crashes right before the profiling completes. The application always crashes when the “Samples processed” dataset around 72% and is always displays one of two messages before the Nsight freezes:
New memory area at … /nvptxJitCompiler64.dll
New memory area at … /nvrtum64.dll
In very rare occurances, I’ve managed to not encounter this error and the report is generated but this seems to happen more than 95% of the times so any indication on why this is happening would be really helpful.This is run on a laptop with a 2070 mobile GPU. I’ve tried to decipher the log file but had no luck so some help would be appreciated.
No, neither a .qdstrm or .qdrep file is created when the profiler fails. Yes, I’m running this from the GUI and the options I have enabled are:
Sample target process
Collect CPU context switch trace
Collect GPU metrics
Collect Vulkan Trace
Interestingly, I find that Nsight Systems also crashes when I try to open up some qdrep files that were generated when I ran the profiler a couple of months ago. I tried unintalling and reinstalling the program assuming it might have been an issue with my local build but that didn’t resolve any issues. I’ve attached the qdrep file that fails to open: Report 1.qdrep (2.3 MB)
Hi adithyavenkatarao
Using NVIDIANsightSystems2021.3.1.54-ee9c30a on my Windows machine, the attached qdrep file opens without issues, I did not get a crash.
Regarding the crash during profiling, have you tried activating/deactivating the features you mentioned? Does the crash appear due to a specific feature?
I am running this on windows. And yes, I’ve tried enabling and disabling all of the features one by one to see if any particular one is causing this issue but no luck. Even running the profiler without any options leads to an application crash. @ztasoulas I am running the exact same version of NsightSystem.
I believe that the issue has fixed itself after I manually removed the Nsight Systems folder under C:/Program Files/NVIDIA Corporation. I noticed that the uninstaller did not remove some of the files from there and just tried removing it all before I reinstalled nsight systems and I’ve not been getting the issue ever since. To be honest, I don’t really understand why this would fix the issue but I can’t complain. If I start getting the same issue again, I’ll post it in this thread. Thanks again @ztasoulas and @hwilper for taking some time to look into this :)