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.