language-tools: IntelliSense is painfully slow

Vue - Official extension or vue-tsc version

v2.1.10

VSCode version

1.96

Vue version

3.5.13

TypeScript version

5.7.2

System Info

System:
    OS: Windows 11 10.0.22631
    CPU: (24) x64 AMD Ryzen 9 5900X 12-Core Processor
    Memory: 35.22 GB / 63.91 GB
  Binaries:
    Node: 20.10.0 - C:\Program Files\nodejs\node.EXE
    Yarn: 1.22.22 - ~\AppData\Roaming\npm\yarn.CMD
    npm: 9.6.6 - C:\Program Files\nodejs\npm.CMD
  Browsers:
    Edge: Chromium (127.0.2651.74)
    Internet Explorer: 11.0.22621.3527

package.json dependencies

No response

Steps to reproduce

Intellisense is slow both in template and in script parts of Vue files. I’ve had a look at the output, and it seems a bunch of the requests are taking a long (multiple seconds) time.

The only thing I’m doing in this test is writing <div, expecting the tag to be closed automatically, and waiting. I see similar results, of requests taking a long time when editing the script part, or anything else essentially.

[Trace - 6:58:22 PM] Sending request 'textDocument/linkedEditingRange - (375)'.
[Trace - 6:58:22 PM] Received response 'textDocument/documentSymbol - (369)' in 2104ms.
[Trace - 6:58:22 PM] Received response 'textDocument/semanticTokens/range - (370)' in 1998ms.
[Trace - 6:58:22 PM] Received notification 'textDocument/publishDiagnostics'.
[Trace - 6:58:22 PM] Received response 'textDocument/inlayHint - (371)' in 1876ms.
[Trace - 6:58:22 PM] Received response 'textDocument/inlayHint - (372)' in 1702ms.
[Trace - 6:58:22 PM] Received response 'textDocument/documentLink - (373)' in 1430ms.
[Trace - 6:58:22 PM] Received response 'textDocument/documentColor - (374)' in 1314ms.
[Trace - 6:58:22 PM] Received response 'textDocument/linkedEditingRange - (375)' in 63ms.
[Trace - 6:58:22 PM] Received notification 'textDocument/publishDiagnostics'.
[Trace - 6:58:22 PM] Sending request 'textDocument/linkedEditingRange - (376)'.
[Trace - 6:58:23 PM] Received response 'textDocument/linkedEditingRange - (376)' in 2ms.
[Trace - 6:58:24 PM] Sending request 'textDocument/linkedEditingRange - (377)'.
[Trace - 6:58:24 PM] Received response 'textDocument/linkedEditingRange - (377)' in 1ms.
[Trace - 6:58:25 PM] Sending notification 'textDocument/didChange'.
[Trace - 6:58:25 PM] Sending request 'textDocument/completion - (378)'.
[Trace - 6:58:25 PM] Received request 'workspace/configuration - (35)'.
[Trace - 6:58:25 PM] Sending response 'workspace/configuration - (35)'. Processing request took 0ms
[Trace - 6:58:25 PM] Received request 'workspace/configuration - (36)'.
[Trace - 6:58:25 PM] Sending response 'workspace/configuration - (36)'. Processing request took 0ms
[Trace - 6:58:25 PM] Sending request 'textDocument/linkedEditingRange - (379)'.
[Trace - 6:58:25 PM] Sending request 'textDocument/signatureHelp - (380)'.
[Trace - 6:58:25 PM] Sending request 'textDocument/foldingRange - (381)'.
[Trace - 6:58:25 PM] Sending request 'textDocument/documentSymbol - (382)'.
[Trace - 6:58:25 PM] Sending request 'textDocument/semanticTokens/range - (383)'.
[Trace - 6:58:26 PM] Sending request 'textDocument/inlayHint - (384)'.
[Trace - 6:58:26 PM] Sending notification '$/cancelRequest'.
[Trace - 6:58:26 PM] Sending request 'textDocument/inlayHint - (385)'.
[Trace - 6:58:26 PM] Sending request 'textDocument/documentColor - (386)'.
[Trace - 6:58:26 PM] Sending request 'textDocument/documentLink - (387)'.
[Trace - 6:58:26 PM] Received response 'textDocument/completion - (378)' in 1332ms.
[Trace - 6:58:26 PM] Received response 'textDocument/linkedEditingRange - (379)' in 1301ms.
[Trace - 6:58:26 PM] Received response 'textDocument/signatureHelp - (380)' in 1226ms.
[Trace - 6:58:26 PM] Received response 'textDocument/foldingRange - (381)' in 1151ms.
[Trace - 6:58:26 PM] Received response 'textDocument/documentSymbol - (382)' in 988ms.
[Trace - 6:58:26 PM] Received notification 'textDocument/publishDiagnostics'.
[Trace - 6:58:26 PM] Sending request 'completionItem/resolve - (388)'.
[Trace - 6:58:27 PM] Received response 'textDocument/semanticTokens/range - (383)' in 1427ms.
[Trace - 6:58:27 PM] Received notification 'textDocument/publishDiagnostics'.
[Trace - 6:58:27 PM] Received response 'textDocument/inlayHint - (384)' in 1306ms.
[Trace - 6:58:27 PM] Received response 'textDocument/inlayHint - (385)' in 1133ms.
[Trace - 6:58:27 PM] Received response 'textDocument/documentColor - (386)' in 894ms.
[Trace - 6:58:27 PM] Received response 'textDocument/documentLink - (387)' in 794ms.
[Trace - 6:58:27 PM] Received response 'completionItem/resolve - (388)' in 581ms.
[Trace - 6:58:27 PM] Sending notification 'textDocument/didChange'.
[Trace - 6:58:27 PM] Sending request 'completionItem/resolve - (389)'.
[Trace - 6:58:27 PM] Received response 'completionItem/resolve - (389)' in 1ms.
[Trace - 6:58:27 PM] Sending request 'textDocument/signatureHelp - (390)'.
[Trace - 6:58:27 PM] Sending notification 'textDocument/didChange'.
[Trace - 6:58:27 PM] Sending request 'completionItem/resolve - (391)'.
[Trace - 6:58:27 PM] Sending notification 'textDocument/didChange'.
[Trace - 6:58:27 PM] Sending notification '$/cancelRequest'.
[Trace - 6:58:27 PM] Sending request 'completionItem/resolve - (392)'.
[Trace - 6:58:27 PM] Received response 'textDocument/signatureHelp - (390)' in 201ms.
[Trace - 6:58:27 PM] Received response 'completionItem/resolve - (391)' in 148ms.
[Trace - 6:58:27 PM] Received response 'completionItem/resolve - (392)' in 36ms.
[Trace - 6:58:27 PM] Sending request 'textDocument/signatureHelp - (393)'.
[Trace - 6:58:27 PM] Received response 'textDocument/signatureHelp - (393)' in 2ms.
[Trace - 6:58:28 PM] Sending request 'textDocument/linkedEditingRange - (394)'.
[Trace - 6:58:28 PM] Received response 'textDocument/linkedEditingRange - (394)' in 2ms.
[Trace - 6:58:28 PM] Received notification 'textDocument/publishDiagnostics'.
[Trace - 6:58:28 PM] Sending notification 'textDocument/didChange'.
[Trace - 6:58:28 PM] Sending request 'textDocument/completion - (395)'.
[Trace - 6:58:28 PM] Sending request 'textDocument/documentSymbol - (396)'.
[Trace - 6:58:28 PM] Sending notification '$/cancelRequest'.
[Trace - 6:58:28 PM] Sending request 'volar/client/autoInsert - (397)'.
[Trace - 6:58:28 PM] Sending request 'textDocument/signatureHelp - (398)'.
[Trace - 6:58:28 PM] Sending request 'textDocument/linkedEditingRange - (399)'.
[Trace - 6:58:28 PM] Sending request 'textDocument/documentSymbol - (400)'.
[Trace - 6:58:28 PM] Sending request 'textDocument/documentColor - (401)'.
[Trace - 6:58:28 PM] Sending request 'textDocument/foldingRange - (402)'.
[Trace - 6:58:28 PM] Sending request 'textDocument/semanticTokens/range - (403)'.
[Trace - 6:58:28 PM] Sending request 'textDocument/inlayHint - (404)'.
[Trace - 6:58:28 PM] Sending notification '$/cancelRequest'.
[Trace - 6:58:28 PM] Sending request 'textDocument/inlayHint - (405)'.
[Trace - 6:58:29 PM] Sending request 'textDocument/documentLink - (406)'.
[Trace - 6:58:30 PM] Received response 'textDocument/completion - (395)' in 1863ms.
[Trace - 6:58:30 PM] Received response 'textDocument/documentSymbol - (396)' in 1841ms.
[Trace - 6:58:30 PM] Received response 'volar/client/autoInsert - (397)' in 1763ms.
[Trace - 6:58:30 PM] Sending notification 'textDocument/didChange'.
[Trace - 6:58:30 PM] Sending notification '$/cancelRequest'.
[Trace - 6:58:30 PM] Sending notification '$/cancelRequest'.
[Trace - 6:58:30 PM] Received response 'textDocument/signatureHelp - (398)' in 1750ms.
[Trace - 6:58:30 PM] Received response 'textDocument/linkedEditingRange - (399)' in 1669ms.
[Trace - 6:58:30 PM] Received response 'textDocument/documentSymbol - (400)' in 1520ms.
[Trace - 6:58:30 PM] Received response 'textDocument/documentColor - (401)' in 1489ms.
[Trace - 6:58:30 PM] Received response 'textDocument/foldingRange - (402)' in 1480ms.
[Trace - 6:58:30 PM] Received response 'textDocument/semanticTokens/range - (403)' in 1376ms.
[Trace - 6:58:30 PM] Received response 'textDocument/inlayHint - (404)' in 1251ms.
[Trace - 6:58:30 PM] Sending request 'volar/client/autoInsert - (407)'.
[Trace - 6:58:30 PM] Sending request 'textDocument/signatureHelp - (408)'.
[Trace - 6:58:30 PM] Received response 'textDocument/inlayHint - (405)' in 1226ms.
[Trace - 6:58:30 PM] Received response 'textDocument/documentLink - (406)' in 932ms.
[Trace - 6:58:30 PM] Received response 'volar/client/autoInsert - (407)' in 59ms.
[Trace - 6:58:30 PM] Received response 'textDocument/signatureHelp - (408)' in 49ms.
[Trace - 6:58:30 PM] Sending request 'textDocument/linkedEditingRange - (409)'.
[Trace - 6:58:30 PM] Received response 'textDocument/linkedEditingRange - (409)' in 2ms.
[Trace - 6:58:30 PM] Sending request 'textDocument/documentSymbol - (410)'.
[Trace - 6:58:30 PM] Received response 'textDocument/documentSymbol - (410)' in 4ms.
[Trace - 6:58:30 PM] Sending request 'textDocument/foldingRange - (411)'.
[Trace - 6:58:30 PM] Received response 'textDocument/foldingRange - (411)' in 3ms.
[Trace - 6:58:30 PM] Received notification 'textDocument/publishDiagnostics'.
[Trace - 6:58:30 PM] Sending request 'textDocument/semanticTokens/range - (412)'.
[Trace - 6:58:30 PM] Sending request 'textDocument/inlayHint - (413)'.
[Trace - 6:58:30 PM] Sending notification '$/cancelRequest'.
[Trace - 6:58:30 PM] Sending request 'textDocument/inlayHint - (414)'.
[Trace - 6:58:31 PM] Sending request 'textDocument/documentColor - (415)'.
[Trace - 6:58:31 PM] Sending request 'textDocument/documentLink - (416)'.
[Trace - 6:58:32 PM] Received response 'textDocument/semanticTokens/range - (412)' in 1672ms.
[Trace - 6:58:32 PM] Received notification 'textDocument/publishDiagnostics'.
[Trace - 6:58:32 PM] Received response 'textDocument/inlayHint - (413)' in 1545ms.
[Trace - 6:58:32 PM] Received response 'textDocument/inlayHint - (414)' in 1373ms.
[Trace - 6:58:32 PM] Received response 'textDocument/documentColor - (415)' in 1167ms.
[Trace - 6:58:32 PM] Received response 'textDocument/documentLink - (416)' in 1090ms.
[Trace - 6:58:32 PM] Received notification 'textDocument/publishDiagnostics'.

What is expected?

Intellisense is completing within a reasonable time (100ms?), both when editing template and script

What is actually happening?

Intellisense is extremely slow, often taking 10s of seconds before completions are available

Link to minimal reproduction

No response

Any additional comments?

No response

About this issue

  • Original URL
  • State: closed
  • Created 2 years ago
  • Reactions: 7
  • Comments: 47 (20 by maintainers)

Most upvoted comments

We have identified the problem and are working on fixing it.

@ludwig801 project size is usually not the reason, even in TypeScript’s checker.ts with 50,000 lines of code, autocompletion can be completed in a few hundred milliseconds. Like I said above, you need to find which differences causing the performance issue.

I understand this. The problem is that this only happens in Vue projects. In TS-only projects I have no problems with performance whatsoever.

Seeing that I’m creating SFC the way I supposed they are to be created (following the official Vue docs) and that I’m importing stuff and doing everything that I’m supposed to, I have to conclude that this issue arise from the Vue language tools and it’s way of handling either TS, <script setup> or something other from the language itself.

In sum, I believe I’m not doing anything wrong with TS, since I have other large TS-only projects working just fine, and without a way to properly debug problematic files or common pitfalls that one might be falling into, it’s difficult do understand where the problem might be in a project with 1000+ files/components.

I have similar issues too. My project is bigger, it goes up to 1.44GB in a single file! image image

Before the actual inspection, no one can assert that he has not made any mistakes. And dichotomy is already a very practical debugging way.

Perhaps, for a small project. For a full platform, such as is my company’s case, is a huge pain in the neck with countless hours of debugging and no assurance of an answer.

I’m not trying to be difficult or snappy, but I have to realistically consider the following: this only happens in a Vue project, with the Vue Language Tools - surely it is common sense to believe that it is not my TS scripting capabilities that are at fault here since, as I’ve mentioned before, I have other full-fledged TS projects which present no issues at all and are quick and performant when editing.

@rigtigeEmil you should gradually eliminate the differences between the two projects through dichotomy and confirm the minimal differences that cause performance problems. Even if we conduct remote investigations, we only do the same thing. Many of the performance reports we received were ultimately found to be caused by project dependencies or poor TS code.

@ludwig801 project size is usually not the reason, even in TypeScript’s checker.ts with 50,000 lines of code, autocompletion can be completed in a few hundred milliseconds. Like I said above, you need to find which differences causing the performance issue.

Is there a way to get debug information out from the extension? About which file(s) could be causing it to hang, if it’s some files in my project that are causing the issue?

I think it would be better to open a new issue.

I’m sorry, but I didn’t understand you completely. What do you mean by “duplicate names” that users should avoid?

Such as:

declare module 'vue' {
	export interface ComponentCustomProperties {
		foo: string;
	}
}

const foo = 1;

Now the type of foo in the template will narrow to never.

@ludwig801 Would you be willing to provide a repo that can reproduce performance issues? I no longer feel any significant performance issues on @rigtigeEmil’s repo, but I believe we still have a lot to do on larger projects.

Oh man, I would really like to be able to do that, but unfortunately this is a company repo, and I cannot share it outside the company…

If I have the time. I shall try to create a bit enough project for this, but it’s really hard to do so now.

Are there no plans in the future for debugging features within the extension itself? Something like log dumps or traces which would allow a user to submit information regarding performance in an “Anonymous” way without having to share project-sensitive information?

@ludwig801 Would you be willing to provide a repo that can reproduce performance issues? I no longer feel any significant performance issues on @rigtigeEmil’s repo, but I believe we still have a lot to do on larger projects.

200MB: image