microsoft / microsoft/vscode-cpptools

Missing include path caused cpptools-srv to grow to 5.5G. Only 400MB needed after missing path was added.

Open
#6,424 17 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug Language Service
Dominant language
TypeScript
Stars
6.2k
Forks
1.7k
Avg merge
14h 46m
Merged PRs (30d)
61

Description

Type: LanguageService

Intellisense is not working in a certain file. I don't know the cause yet so I am not able to make a simple repro.

I see in the logging

Failed to read response from server: 20
Resetting IntelliSense server: C:\SOMEFILE.CPP

In the extension host logging, I see

[2020-11-02 15:37:49.425] [exthost] [error] onWillSaveTextDocument-listener from extension 'ms-vscode.cpptools' threw ERROR
[2020-11-02 15:37:49.425] [exthost] [error] Error: timeout
	at Timeout._onTimeout (c:\Program Files\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:638:581)
	at listOnTimeout (internal/timers.js:531:17)
	at processTimers (internal/timers.js:475:7)

But I get this message when opening most files so I dont think this is the cause.

Is there a way that I can get more info/logging on what is causing it to fail?

Extension Version 1.1.0-insiders3: October 22, 2020

Version: 1.50.1 (system setup)
Commit: d2e414d9e4239a252d1ab117bd7067f125afd80a
Date: 2020-10-13T15:06:15.712Z
Electron: 9.2.1
Chrome: 83.0.4103.122
Node.js: 12.14.1
V8: 8.3.110.13-electron.0
OS: Windows_NT x64 10.0.17763

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the reported IntelliSense failure in SOMEFILE.CPP and the cpptools extension-host logs, including the failed response and timeout messages. Reproduce the server reset or memory growth if possible, then use additional logging to identify the missing include path or failing language-service operation. Done means the cause is isolated and a focused fix or diagnostic path is identified.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp, typescript
Domain
developer-experience, tooling
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.