IntelliSense Stops Working - cancelled sequence number

[waderyan]

There are open issues on IntelliSense problems in VS Code. The commonality is IntelliSense stops working. I could use some guidance on where I can look to get to the bottom of this.

Related Issues

• No IntelliSense for single file.  vscode#11260
• Word completion is not working yo node-express vscode#11258
• Javascript Intellisense not working vscode#11505
• TypeScript Language Support silently stops vscode#12141
• Intellisense doesn't work on JavaScript file until I change language mode vscode#11938
• intellisense not working for Javascript files stored in sharepoint document library vscode#12350
• Code helper eat 100% and intellisense not working vscode#13294
• Typescript suggestions very often stops working until I restart vs code vscode#13346
• TSServer crash vscode#13335
• The TypeScript language service died unexpectedly 5 times in the last 5 Minutes. Please consider to open a bug report. vscode#14159
• Better handling of TSServer issues vscode#14230

I opened two of the issues as I observed them. The commonality with all many of issues is an output that includes the phrase "canceled request with sequence number x"

What could be causing this?
Are there other logs I can look at to try and debug the problem?

[waderyan]

I'm seeing this again today in the same ways described in the above issues.

I am also seeing it in a new way. I am trying to recreate the issue described here. The process involves a symbol rename symbol operation.

Note that there is only one small file in bin

[dbaeumer]

If requests can be canceled inside VS Code that means they are still in the VS Code's queue. To allow cancelation we only sent requests to the tsserver one by one. In this situation it means that the tsserver is busy processing a request. @waderyan if this happens is there any unusual CPU usage with the tsserver?

[dbaeumer]

In the specific example the quick info request never returns hence we don't send the rename request over the wire.

[dbaeumer]

@waderyan do you have any errors in the dev console.

[mhegazy]

Can you share the tsserver log in these cases?

[waderyan]

@mhegazy where is the tsserver log? Is it different than what I'm seeing in the output window?

@dbaeumer I will grab a screenshot of the dev console when I see it again. I have checked before and haven't seen any errors.

[mhegazy]

first you need to set the environment variable TSS_LOG=-level verbose. there should be a log file written next to tsserver.js that would have the form of .log[0-9]+

[waderyan]

I have not been able to reproduce this issue for the last couple of days. This issue came into day, and it might be related - microsoft/vscode#11938

Asked OP to follow the advise on capturing logs.

[waderyan]

@mhegazy setting the env variable for logging is not working for me.

Am I missing something?

[mhegazy]

that is mac? i am not a mac user, but i guess you should be are you using setenv to set it... or something

[waderyan]

This came up again today. Repeated twice. Here were the steps.

mkdir test
cd test
yo node-express
# choose no for everything

code-insiders .

Go to app.js

Type express.

Note I am on release-2.0.5 bits. I was testing the auto acquire typings experience.

[waderyan]

@mhegazy I setup the env variable properly. Can I specify the location for the log file?

[waderyan]

@mhegazy I'm not seeing the log file in the location of tsc.js. Please advise.

[mhegazy]

I setup the env variable properly. Can I specify the location for the log file?

yes, it should be something of the form -log verbose -file filepath

[mhegazy]

I could not get this to repro locally using this yoman template. are there other things you did after opening app.js?

[waderyan]

I did not do anything after opening app.js.

[waderyan]

Saw the same issue today recreating @Mousetrap's issue here.

This is what I saw in the TypeScript output.

See TSServer exited with code: 7. Do you know what that could be from?

I have the env variable setup correctly but I'm not seeing a log file. If someone could take a look at this too, that would be helpful.

export TSS_LOG="-log verbose -file /Users/waander/.tslog"

Also tried

export TSS_LOG="-level verbose -file /Users/waander/.tslog"

export TSS_LOG="-level verbose -file '/Users/waander/.tslog'"

[ianmurrays]

I'm constantly getting this error now for some reason.

TSServer exited with code: unknown

macOS 10.11.6
VSC 1.8.0

Using the global typescript installation gets rid of the error though:

{
   "typescript.tsdk": "/Users/myuser/.nvm/versions/node/v4.4.0/lib/node_modules/typescript/lib"
}

[vladima]

@ianmurrays can you please share a repro so we can try to isolate the root cause of the problem?

[ghost]

Just when opening vscode with a file. After this error every request gets canceled.

[Trace - 10:17:47] Sending request: navtree (4). Response expected: yes. Current queue length: 2
Arguments: {}
[Trace - 10:19:26] TypeScript Service: canceled request with sequence number 16
[Error - 10:20:33] TSServer exited with code: 3
[Error - 10:20:33] 'navtree' request failed with error.
Error: Service died.
    at c:\Program Files (x86)\Microsoft VS Code\resources\app\extensions\typescript\out\typescriptServiceClient.js:442:46
    at Array.forEach (native)
    at TypeScriptServiceClient.serviceExited (c:\Program Files (x86)\Microsoft VS Code\resources\app\extensions\typescript\out\typescriptServiceClient.js:441:37)
    at ChildProcess.<anonymous> (c:\Program Files (x86)\Microsoft VS Code\resources\app\extensions\typescript\out\typescriptServiceClient.js:362:35)
    at emitTwo (events.js:111:20)
    at ChildProcess.emit (events.js:191:7)
    at Process.ChildProcess._handle.onexit (internal/child_process.js:215:12)
[Info  - 10:20:33] Using tsserver from location: c:\Program Files (x86)\Microsoft VS Code\resources\app\extensions\typescript\node_modules\typescript\lib\tsserver.js

[mhegazy]

@con-ssc do you have a consistent repro for this?

[ghost]

No, it is a customer project.

[ghost]

I also encounter this a lot, when not starting as admin.
"typescript": "^2.1.5",

[Info  - 08:23:01] Using tsserver from location: d:\repositories\git\aurelia-subscription-form\node_modules\typescript\lib\tsserver.js
[Error - 08:23:01] TSServer exited with code: 1

[mhegazy]

Can you share the tssever log file. see https://github.com/Microsoft/TypeScript/wiki/Standalone-Server-(tsserver)#logging.

you need to set the TSS_LOG environment variable to -level verbose -file <path to file>, start VSCode from the same console, and share the log with us.

[ghost]

I'm afraid that is not possible since the tsserver is logging the whole file content and I can publish those files.

[mhegazy]

feel free to redact parts you do not want to share. we care most about the set of actions before the error occurs.
Also we would be happy to sign any necessary NDA's to get access to the log and/or the code base.

[pocesar]

getting "TSServer exited with code: 3" with 2.2.0-dev.20170209 randomly on a plain clone of https://github.com/rangle/typescript-react-redux-example

not sure if it's a problem with VSCode or TS nightly. When I try to see the dev tools on vscode, the editor freezes

[mhegazy]

@pocesar, I am unable to reproduce this locally on latest. is this still an issue? if so can you share any more information to help reproduce the issue.

[mhegazy]

There has not been any actionable leads in this issue. closing for now. If you are experiencing similar symptoms, please file a new issue and provide us with a project that you experience the server crash on, and/or tssever log file.