"Go to Definition" and "Peek Definition" functionalities have stopped working

[donfiguerres]

This problem which seems to have started from the last update (I noticed this problem on May 22, 2017). The "Go to Definition" and "Peek Definition" functionalities have stopped working. Click and hover over the symbol also does not show the symbol definition. Please refer to screenshot below.

This might be related to #743

[bobbrow]

Thanks for reporting this. The Loading... message comes from VS Code when the extension is not responding. This could be for any number of reasons, so I'll ask a few questions and we'll go from there.

• What OS are you using?
• Do you see any Microsoft.VSCode.CPP.Extension.* or Microsoft.VSCode.CPP.IntelliSense.Msvc.* processes running?
  • If so, what is their memory footprint?

I have seen a rare issue with the extension where it will crash and VS Code automatically restarts it, but does not ever successfully send it messages again. Restarting VS Code will make it start working again, but I am trying to find a way to reproduce the problem so I can debug it and fix it.

[MAntal001]

try to check this thread #667. the solution might help

[bobbrow]

The fix for #667 is included in 0.11.1. This could be some other bug in the JavaScript, but it would be a bug we haven't identified yet.

[jhsterling]

I have this problem as well. Is it possible to back up to the previous revision?

[bobbrow]

If you are persistently having this problem, we would like to help you debug through it, but we also understand that you have work to do and are trying not to get in your way. If the extension continues to be unresponsive, go to your settings and add the following: "C_Cpp.intelliSenseEngine": "Tag Parser". This will revert you to the previous behavior.

VS Code does not currently provide a way to install a specific version of an extension.

[UR3IQO]

@bobbrow I have the same issue. Switching to the old IntelliSense engine (by adding "C_Cpp.intelliSenseEngine": "Tag Parser" ) solves the problem.

I use Windows 8.0, VSCode 1.12.2.

I do not know if it is relevant to the problem, but there is an error in the log:

/C:/Program Files (x86)/Microsoft VS Code/resources/app/out/vs/workbench/electron-browser/workbench.main.js:29 [Extension Host] (node:7260) DeprecationWarning: os.tmpDir() is deprecated. Use os.tmpdir() instead.
d.logExtensionHostMessage @ /C:/Program Files (x86)/Microsoft VS Code/resources/app/out/vs/workbench/electron-browser/workbench.main.js:29

VS Code does not currently provide a way to install a specific version of an extension.

I always save old extension directory, so I can switch several versions of extension manually.

[donfiguerres]

@bobbrow Answers are below.

• What OS are you using?
  • Windows Server 2012 R2
• Do you see any Microsoft.VSCode.CPP.Extension.* or Microsoft.VSCode.CPP.IntelliSense.Msvc.* processes running?
  • Yes. I see both
• If so, what is their memory footprint?
  • see below
    

[bobbrow]

Thanks. Unfortunately, this appears to be something else. Does the CPU usage of either process go up at all when you make edits to the file that is open or do they both stay idle?

If the CPU usage does not increase at all, it may be stuck in a deadlock somewhere. If you are able to attach to the two processes and save a mini-dump of them for us (you can drop them into this issue), that would be super helpful.

If you use VS Code's reload window command, does the extension work again or is this something that persists? Reloading the window should unload and reload the extension.

[UR3IQO]

@bobbrow ,

What OS are you using?

Windows 8.0

Do you see any Microsoft.VSCode.CPP.Extension.* or Microsoft.VSCode.CPP.IntelliSense.Msvc.* processes running?
If so, what is their memory footprint?

There is only Microsoft.VSCode.CPP.Extension.exe :

Does the CPU usage of either process go up at all when you make edits to the file that is open or do they both stay idle?

Yes, it goes up when I edit code.

If you use VS Code's reload window command, does the extension work again or is this something that persists?

The problem is persistent.

[donfiguerres]

Unfortunately, I'm a bit busy so I might not be able to help debugging as of this time.
To answer your questions

• the CPU usage does not go up for me when I try to edit a file. I'm not sure if I'm just not noticing it.
• the problem is persistent eve if I use the reload window command.

[bobbrow]

@sov1178, yours looks like the bug I was referring to above that I've been trying to catch in a debugger. When you reload the window, is this process terminated and replaced with a new one? What I expect to see for this bug is that the new process will spawn a Microsoft.VSCode.CPP.IntelliSense.Msvc.exe process, but then both new processes will be torn down and replaced by a single Microsoft.VSCode.CPP.Extension.exe process with a low memory footprint that doesn't respond to editor commands as it should.

@donofthenorth, If the problem is persistent and you need to get back to work, please switch back to the old IntelliSense engine by adding the "C_Cpp.intelliSenseEngine": "Tag Parser" setting to your settings.json. Thank you for your help.

[UR3IQO]

@bobbrow

When you reload the window, is this process terminated and replaced with a new one?

Yes

What I expect to see for this bug is that the new process will spawn a Microsoft.VSCode.CPP.IntelliSense.Msvc.exe process...

No, I do not see any attempts to start Microsoft.VSCode.CPP.IntelliSense.Msvc.exe process:

What do you think about the error in the log? When I switch to "Tag Parser" there are no errors in the log.