NSight hangs =(

Hi everyone!

I have some problems with NSight: today it began to hang (after VS 2015 auto-update to 14.0.23107.178).

When I press “Start graphics debugging”, my process starts to consume CPU, and window did not appear.
Pressing “Pause debugging” don’t even show disassembly.

My process is 64 bit, DX11, MFC SDI, runs under Win10, VS 2015 update3.

After upgrade to latest version of NSight and NV driver, the problem has not gone.
I ran XPerf, and saw this stack:
https://www.dropbox.com/sh/0eu46g4wu76npgj/AACr44w9HsR7Cgb-gd5tToj1a?dl=0
Here is etl of the problem. (The link will be valid till 2016.12.01)

I don’t have symbols to NVidia dlls, but probably Nvidia engineers do.
Also in the ETL you can find full system configuration.

It is very suspicious to see nvoglv64.dll (I don’t have OGL linked to my app)
Without attached Nsight debugger, my app runs OK.

Does anyone saw something similar and know how to fix this?
Thanks in advance!
xperf.png

I am seeing the same issue, did you ever get a resolution?

DX11, 32bit, WIN10 VS2015 update 5 with a GTX 980. I have 2 GTX 980s installed but SLI is disabled.

My previous version of app was MFC, SDI + MFC ribbon.
Now have I completely rewritten the app to pure winapi, and problem gone.
It seems NSight does not work well with MFC ribbon =(

So for me problem is solved, but for NSight - probably not.

Hi HappySDE,

Nsight supports MFC, can we have your sample to do some local repro, then we can identify the problem?

Thanks,
Letitia

I cannot give you my app, but there is much better way to reproduce the problem:

  1. Create SDI MFC app (with ribbon)
  2. Re-Target project to 10.0.14393 (I do not have any early versions of SDK, so maybe it’s unnecessary)
  3. Compile.
  4. NSight->Start graphics debugging.
    This time I tried x86, Debug and Release modes.

Window will not appear, one core will be busy with stack:

Line #, Process, Thread ID, Stack, Count, Weight (in view) (ms)
8, , , | |- Nvda.Graphics.Interception.dll!, 9453, 9,455.990653
9, , , | | |- nvoglv32.dll!, 9448, 9,450.977973
10, , , | | | |- nvoglv32.dll!, 9446, 9,448.978339
11, , , | | | | nvoglv32.dll!, 9446, 9,448.978339
12, , , | | | | |- KernelBase.dll!SwitchToThread, 6647, 6,649.323733
13, , , | | | | |- ntdll.dll!NtYieldExecution, 1727, 1,727.270851
14, , , | | | | |- nvoglv32.dll!, 922, 922.304064

For simple Winapi project it will not be the case.

This link will be valid till 2017.01.15:
https://www.dropbox.com/sh/dxpu6dmcq1p4ben/AACpJXKuTDivGXmn3S5HeZB-a?dl=0

MFCApplication1.zip - the MFC app.
2016.12.22-15.56.08.368.etl - ETL trace

The other issue I found with NSight and MFC:

My Game-app works well with NSight and I can profile it with NSight.
In current phase I decided to make config as another, MFC-dlg based process, and start it via CreateProcess (I have no resource to create own-rendering dialogs/buttons).

So, when I run my game under NSight debugger, it works well, and without hangs.
When I spawn Config.exe, under NSight, process starts, but it’s window does not appear.
One core became busy for 100%.
The game runs OK.

Line #, Process, Thread ID, Stack, Count, Weight (in view) (ms)
28, , , | Nvda.Nexus.Injection.dll!, 8926, 8,946.665925
29, , , | |- Nvda.Graphics.Interception.dll!, 8894, 8,914.487088
30, , , | | Nvda.Graphics.Interception.dll!, 8894, 8,914.487088
31, , , | | Nvda.Graphics.Interception.dll!, 8894, 8,914.487088
32, , , | | Nvda.Graphics.Interception.dll!, 8894, 8,914.487088
33, , , | | Nvda.Graphics.Interception.dll!, 8894, 8,914.487088
34, , , | | |- Nvda.Graphics.Interception.dll!, 8888, 8,908.499589
35, , , | | | Nvda.Graphics.Interception.dll!, 8888, 8,908.499589
36, , , | | | |- Nvda.Graphics.Interception.dll!, 8887, 8,907.499285
37, , , | | | | |- Nvda.Graphics.Interception.dll!, 8885, 8,905.496666
38, , , | | | | | |- Nvda.Graphics.Interception.dll!, 8386, 8,405.922777
39, , , | | | | | | |- nvoglv64.dll!, 8382, 8,401.922505
40, , , | | | | | | | nvoglv64.dll!, 8382, 8,401.922505
41, , , | | | | | | | |- nvoglv64.dll!, 8380, 8,399.861170
42, , , | | | | | | | | nvoglv64.dll!, 8380, 8,399.861170
43, , , | | | | | | | | |- KernelBase.dll!SwitchToThread, 8096, 8,115.253924
44, , , | | | | | | | | | |- ntdll.dll!NtYieldExecution, 7217, 7,233.964564
45, , , | | | | | | | | | | |- ntoskrnl.exe!KiSystemServiceUser, 3548, 3,556.201856

When I stop NSight debugging, Game.exe stops normally, but Config.exe continues to run (without it’s main window created).

The only thing I can do - is to kill the Config.exe in process explorer.

So there is another ETL for this case:
2016.12.22-16.11.27.658.etl ( https://www.dropbox.com/sh/dxpu6dmcq1p4ben/AACpJXKuTDivGXmn3S5HeZB-a?dl=0 )
Game = Doom.exe
Config = DoomConfig.exe

Thanks, we’ll do some local repro and identify the problem.