SQLite crash/corruption when database is on a remote filesystem

[draeger-charles-wilson]

I've just updated to 1.20.1 / 0.15.0 and foolishly deleted the previously working versions whose numbers I do not recall (late December updates). The auto update of the cpptools extension failed to be able to download its bits and so I installed it from the (self-contained) VSIX file. Unfortunately, the extension seems possessed to make a JSON RPC call which fails. The result being no Intellisense information and no compilation capability.

OS: Windows 7
cpptools 0.15.0
Version 1.20.1
Commit f88bbf9137d24d36d968ea6b2911786bfe103002
Date 2018-02-13T15:34:36.336Z
Shell 1.7.9
Renderer 58.0.3029.110
Node 7.9.0
Architecture x64

steps:
open C file

[Error - 1:28:13 PM] Request textDocument/codeAction failed.
Error: Connection got disposed.
at Object.dispose (C:\Users\wilson.vscode\extensions\ms-vscode.cpptools-0.15.0\node_modules\vscode-jsonrpc\lib\main.js:825:25)
at Object.dispose (C:\Users\wilson.vscode\extensions\ms-vscode.cpptools-0.15.0\node_modules\vscode-languageclient\lib\client.js:57:35)
at LanguageClient.handleConnectionClosed (C:\Users\wilson.vscode\extensions\ms-vscode.cpptools-0.15.0\node_modules\vscode-languageclient\lib\client.js:1864:38)
at LanguageClient.handleConnectionClosed (C:\Users\wilson.vscode\extensions\ms-vscode.cpptools-0.15.0\node_modules\vscode-languageclient\lib\main.js:78:15)
at closeHandler (C:\Users\wilson.vscode\extensions\ms-vscode.cpptools-0.15.0\node_modules\vscode-languageclient\lib\client.js:1852:18)
at CallbackList.invoke (C:\Users\wilson.vscode\extensions\ms-vscode.cpptools-0.15.0\node_modules\vscode-jsonrpc\lib\events.js:71:39)
at Emitter.fire (C:\Users\wilson.vscode\extensions\ms-vscode.cpptools-0.15.0\node_modules\vscode-jsonrpc\lib\events.js:135:36)
at closeHandler (C:\Users\wilson.vscode\extensions\ms-vscode.cpptools-0.15.0\node_modules\vscode-jsonrpc\lib\main.js:221:26)
at CallbackList.invoke (C:\Users\wilson.vscode\extensions\ms-vscode.cpptools-0.15.0\node_modules\vscode-jsonrpc\lib\events.js:71:39)
at Emitter.fire (C:\Users\wilson.vscode\extensions\ms-vscode.cpptools-0.15.0\node_modules\vscode-jsonrpc\lib\events.js:135:36)
[Error - 1:28:13 PM] Connection to server got closed. Server will not be restarted.

[bobbrow]

We have self-contained downloadable versions available here: https://github.com/Microsoft/vscode-cpptools/releases

[draeger-charles-wilson]

As stated in the problem, I downloaded the self-contained VSIX version of the extension.

[bobbrow]

Ok. I read the and here to mean that you were still talking about the VSIX that failed.

The auto update of the cpptools extension failed to be able to download its bits and I installed it from the VSIX file

In that case, it looks like the extension is crashing. Can you add "C_Cpp.loggingLevel": "Information" to your settings.json and then restart VSCode? Then paste any logging messages you see in the Output window for the "C/C++" channel here. In the meantime, I'll take a look at the codeAction event handler to see if anything stands out.

[draeger-charles-wilson]

Did that, and the output is provided. I put the logging level setting in my user setting file.

[bobbrow]

Where did you provide the output? The messages you pasted at the beginning of this issue are not from the "C/C++" Output channel.

[draeger-charles-wilson]

The error provided was from the output window. Snip now attached.

[sean-mcmanus]

@draeger-charles-wilson That is not the C/C++ output channel.

[draeger-charles-wilson]

My mistake. How do I access the C/C++ output channel?

[bobbrow]

It's in the drop down box to the right of the tabs (where "cpptools: PMA" is in your screenshot). If you're using a multi-root workspace it will be "C/C++: PMA", otherwise it should just be called "C/C++".

[draeger-charles-wilson]

Not seeing it.

Note: I restarted and it attempted to load the language server 5 times. Apparently yielding the 5 entries in the menu.

[sean-mcmanus]

It looks like our language service process is crashing 5 times and causing the extension to not be loadable. I don't know what could be causing this. I'm not aware of any widespread crashing on Windows (0.15.0 fixed our previous high hitting Windows crashes). Maybe it's some issue with Win7? Did you install the 0.15.0 vsix or an older one?

[draeger-charles-wilson]

I have uninstalled and reinstalled from the current bits. Is it trying to phone home for something? We have a very aggressive firewall. Could this be a telemetry issue? I'd submitted an issue previously where the default for telemetry was set to not send by default for similar reasons.

[sean-mcmanus]

I don't think telemetry code can be causing any issues -- you can disable telemetry via setting telemetry.enableTelemetry to "false".

[bobbrow]

JSON RPC is for inter-process communication, not telemetry. You might want to try attaching to the extension process on launch and then sending us a callstack. There is a good article on setting up WinDbg to attach on process launch. The process you want to attach to is Microsoft.VSCode.CPP.Extension.exe.

[draeger-charles-wilson]

I've not used WinDbg myself and while I was able to get it to stop on launch of the extension, continuing execution merely saw that process sit. If I dismissed WinDbg itself, this was repeated 4 more times and then the final error message would appear.

I took another look at my c_cpp_properties.json and discovered that one of my mounted volumes referenced in the 'includePath' section was no longer on-line. When I switch the path to a volume that was present, the error still occurred, but the C/C++ log appeared in the output dropdown.

The contents of that window is:

IntelliSense Engine = Default.
The extension will use the Tag Parser for IntelliSense when #includes don't resolve.
Autocomplete is enabled.
Error squiggles are enabled.
File exclude: **/.git
File exclude: **/.svn
File exclude: **/.hg
File exclude: **/CVS
File exclude: **/.DS_Store
File exclude: **/.vscode
Search exclude: **/node_modules
Search exclude: **/bower_components
Search exclude: **/.vscode
IntelliSense Engine = Default.
The extension will use the Tag Parser for IntelliSense when #includes don't resolve.
Autocomplete is enabled.
Error squiggles are enabled.
File exclude: **/.git
File exclude: **/.svn
File exclude: **/.hg
File exclude: **/CVS
File exclude: **/.DS_Store
File exclude: **/.vscode
Search exclude: **/node_modules
Search exclude: **/bower_components
Search exclude: **/.vscode
IntelliSense Engine = Default.
The extension will use the Tag Parser for IntelliSense when #includes don't resolve.
Autocomplete is enabled.
Error squiggles are enabled.
File exclude: **/.git
File exclude: **/.svn
File exclude: **/.hg
File exclude: **/CVS
File exclude: **/.DS_Store
File exclude: **/.vscode
Search exclude: **/node_modules
Search exclude: **/bower_components
Search exclude: **/.vscode
IntelliSense Engine = Default.
The extension will use the Tag Parser for IntelliSense when #includes don't resolve.
Autocomplete is enabled.
Error squiggles are enabled.
File exclude: **/.git
File exclude: **/.svn
File exclude: **/.hg
File exclude: **/CVS
File exclude: **/.DS_Store
File exclude: **/.vscode
Search exclude: **/node_modules
Search exclude: **/bower_components
Search exclude: **/.vscode
IntelliSense Engine = Default.
The extension will use the Tag Parser for IntelliSense when #includes don't resolve.
Autocomplete is enabled.
Error squiggles are enabled.
File exclude: **/.git
File exclude: **/.svn
File exclude: **/.hg
File exclude: **/CVS
File exclude: **/.DS_Store
File exclude: **/.vscode
Search exclude: **/node_modules
Search exclude: **/bower_components
Search exclude: **/.vscode

So, this appears to be one bug. I'm going to continue tinkering with the properties file for a bit.