Nsight immediate abnormal termination

I’m pretty unfamiliar with all this, so please bear with me. Just trying to work with some graphics filters.

I’ve selected a local application to run in Nsight user properties, but when I try to “start graphics debugging” I get an immediate error “connection to the Nsight monitor was terminated abnormally”, and Nsight has crashed. The application GUI does not appear but it is visible in task manager.

I have up to date VS 2017, Nsight, and GPU drivers, and I’m using a 1080ti. I have not been able to get past this point in any case whatsoever. Nsight settings are left at defaults, though I’ve messed with them and had no results.

I also have similar issues.

I am using Windows 10 16299.248, up to date VS 2017, Nvidia driver version 390.65, Nsight version 5.5.0.18014 and GTX 1080 ti.

I have tried to use tutorial 2 of Direct3D11Tutorials in https://github.com/walbourn/directx-sdk-samples. Which triggers the problem.

I did a fresh reinstall of Nsight and I did not change any settings.

Hi,

Are your guys mean the Nsight monitor crash like this thread? https://devtalk.nvidia.com/default/topic/1028659/nsight-visual-studio-edition/nsight-monitor-crash-on-5-5/

Thanks
An

I do not think so, my callstack window seems to be empty.

Hi contact.nanderson,

It’s hard to say why, do you set the Nsight configuration about exe’s path and its working directory properly? The crash you mean from which, your app crash or Nsight crash (Nsight monitor or Nsight host (visual studio))?

Thanks
An

Hi smallzzy,

I tried the same sample, tutorial02, it looks OK in my side, both tutorial02 and Nsight host(visual studio) and monitor doesn’t show crash.

Thanks
An

The configuration is set correctly. I have talked to people who have successfully debugged the exact same application, and I have followed their configuration. I even tried moving the application to the root directory and updating the configuration just in case the path was too long.

This seems to be system-specific, but I cannot confirm that as I have only one system available to me.

The error is “connection to the Nsight monitor was terminated abnormally”, which indicates that it’s the monitor which is crashing. Visual Studio is still running (and the border is orange, indicating that debugging is in process), and I can see the application name in Task Manager, but there is no window and the application doesn’t seem to be doing anything (0% cpu usage).

I’ll take a look at those tutorial files and see if I can get them to work. I did try a couple other applications initially, but I could have easily been mis-configuring those.

I encounter the same error with the tutorial after building the project. Here’s a screenshot what what it looks like: https://imgur.com/a/z48c1

I encounter this error after a clean install of visual studio and nisght and after changing the ports and security settings for nsight within both the visual studio host and within the application monitor. The only other error I ever get is if I mis-configure nsight.

Hi contact.nanderson,

“connection to the Nsight monitor was terminated abnormally” more means the connection lost, but not Nsight monitor crashed, just check the Nsight monitor process still exist on the machine that you want to debug on.

Thanks
An

It does not. :P

Thanks

Hi contact.nanderson,

Sorry that you meet this. From the sshot, I see that you try to connect from your localhost to DESKTOP-4SABGSL machine, and IIUC, the monitor just crashed on DESKTOP-4SABGSL machine, right?

Can you launch the sample on your localhost machine?
If you don’t launch the sample, but just run the Nsight monitor on your system, does it crash?
If any chance, that you take a try on another machine, does the crash happen?

Thanks
An

Yes, I’m trying to connect to the localhost on my machine, which is identified as DESKTOP-4SABGSL, and the monitor seems to be immediately crashing. As evidence for this, icon briefly appears in the tray, but the process can’t be found in task manager afterwards.

  • If I launch the tutorial through the normal debugger (not graphics debugging) it works correctly, no issues.
  • If I simply open the windows start menu and type Nsight and launch the Nsight Monitor, I am able to launch and configure it - it even says that it's working correctly. However, whether or not the monitor is already running before I attempt to start graphics debugging, it still crashes and no Nsight processes can be found in the task manager afterwards.
  • The only other machine I have available to me is a dual-core laptop with integrated Intel graphics - I could try it there if that's not an issue? This laptop is normally just used for light applications, so I have no idea what it can and can't do.

Thanks

Hi contact.nanderson,

Can you take a try for this:

  • launch nsight monitor
  • attach some debugger like Visual Studio or Windbg to the monitor process
  • run Nsight and launch some sample
  • the debugger should catch the crash, what about the callstack and dump file?

Thanks
An

I had some strange behavior with the two instances of visual studio I had open. The one I had attached to the Monitor went into break mode as soon as I selected “Start Graphics Debugging” in the other, and that one didn’t respond until I clicked “continue” in the first. However, after clicking “continue”, I got the usual messages and nsight crashed. The instance of Visual Studio which had been attached to Nsight was now unattached.

I’m not sure where the dump file would be located, and I don’t know how to access the callstack after the monitor crashes, as the callstack window in visual studio disappears.

However, there are contents in the “output” window which look like they might be useful: https://pastebin.com/pqfd3rTP

In particular the lines

An unhandled exception of type 'System.NullReferenceException' occurred in Nvda.Messaging.Interop.dll
Object reference not set to an instance of an object.

Let me know if those are of use, or how I can find the dump file / record the callstack.

Thanks

P.S. I may not be setting up the tutorial entirely correctly for nsight, come to think of it, as it’s hard to confirm when I get the same error regardless of what I do. However starting debugging normally through V.S. does correctly load the window with a properly rendered triangle, and is, as far as I can tell, working correctly.