Vscode intellisense too slow

By using our site, you acknowledge that you have read and understand our Cookie PolicyPrivacy Policyand our Terms of Service. Stack Overflow for Teams is a private, secure spot for you and your coworkers to find and share information. I am using VSCode for more than a year and never faced this problem.

I have to wait for like 2 minutes on first access to IntelliSense. So every time I open a file, I have to wait for like 2 to 3 minutes before I can see suggestions. When I open Project, I get these messages, which is totally fine I guess.

It's only for the first 10 seconds. What I tried: I disabled all my extensions, reinstalled VScode, reinstall Windows I'm using Windows 10downgrade to previous version and even change my system but still, nothing works. Learn more. Asked 4 months ago. Active 4 months ago. Viewed times. After initialization is finish, it still keeps loading for the next 2 minutes. Arsalan Khattak Arsalan Khattak 3 3 silver badges 12 12 bronze badges.

If you see this with all extensions disabled, please file a bug report. A similar thing goes for linter rules, but you've already noted that you turned off extensions. Active Oldest Votes. Sign up or log in Sign up using Google. Sign up using Facebook. Sign up using Email and Password. Post as a guest Name.

Email Required, but never shown. The Overflow Blog. Tales from documentation: Write for your clueless users.

vscode intellisense too slow

Podcast a conversation on diversity and representation. Upcoming Events. Featured on Meta. Feedback post: New moderator reinstatement and appeal process revisions. The new moderator agreement is now live for moderators to accept across the….

Subscribe to RSS

Allow bountied questions to be closed by regular users. Hot Network Questions. Question feed. Stack Overflow works best with JavaScript enabled.VS becomes unresponsive when reloading browser while editing cshtml 1 Solution.

Visual Studio Intellisense changes contents when typing too fast 1 Solution. VS Start Window does not appear in experimental instance 0 Solution. Typescript Intellisense and compilation stops working every once in a while 1 Solution. Spurious C " is not the pdb that was used when this precompiled header was created, recreate the precompiled header" 1 Solution. Debugging pandas hangs Visual studio if incorrect column name 2 Solution.

Black Lives Matter. This site uses cookies for analytics, personalized content and ads. By continuing to browse this site, you agree to this use. Learn more. Developer Community. Show comments This issue is read only, because it has been in Closed—Fixed state for over 90 days.

It was closed for days. Add comment. Feedback Bot Feb 22, at AM. Feedback Bot Mar 06, at AM. Feedback Bot Mar 22, at AM.

Chuanshan Ma Apr 17, at AM. Jon Wilson Apr 19, at PM. David Harper Apr 30, at PM. Fernando G. May 02, at AM. John Baker May 03, at AM. Rimon Erez May 13, at PM. Reuben Allott May 18, at PM. Javad Zabihi May 29, at AM. Sami Kuhmonen Aug 18, at PM. Alphonse Giambrone Aug 20, at AM.

Paul Stancer Feb 21 at PM. This issue has been closed for over 90 days. If we haven't resolved this issue for you, please report a new problem.

Yes, it works. No, I tried everything.

Developer Community

Show reactions 8 Share. I have installed the fix by upgrading to the latest version of Visual Studio. The issue is still not fixed:. No reactions yet. Did the solution above work for you?GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community. Already on GitHub? Sign in to your account. Tried disabling all extensions, doing a fresh install, and installing the Insider version. IntelliSense still takes more than 3 seconds to suggest anything, even taking more than 30 seconds to remove the red underline after changing some code quickly.

I don't think it's a hardware issue as this is a new MacBook Pro that I just bought, but I can't figure out how to solve this and it's driving me crazy. I'm working on a Gatsby project and whenever I type anything, IntelliSense takes more than 3 seconds to suggest anything. VS Code version: Code 1. I have no idea why it takes them soo long to fix this issue. It's already like this for me since two weeks and it's such an integral part of the software. Hi RMacfarlanethanks for chiming in.

I guess the issue is project related as I just tried opening a React Native project and IntelliSense worked as expected there.

vscode intellisense too slow

Thank you for pointing this out. I have no idea why I haven't tried it myself. Works like a charm. Can confirm I experienced the same issue with 1. Rolling back to 1. If I for example added a new unused import it would take a good 4 seconds for IntelliSense to realise the imported variable was unused and to highlight it accordingly. After rolling back this is near instant. Thank you for the suggestion BjoernRavehope this gets fixed in a future release.

I see you've closed it but rolling back to a previous version isn't a resolution. Yeah, you're right vaunus. I'll reopen the issue and hope someone from the team is able to help. Isn't this issue the same as ? If it is, msallent could you please confirm which version introduced the problem? That would be great! The only extension I have installed so far is Vetur. For example, typing ml and then hitting tab should produce margin-left: ;but I'm consistently getting margin: ; instead because its too slow to react to my keypress.

Have checked my settings, and the delay on IntelliSense was set to 10but even changing this to 0 provides this very slow response. I've also encountered this issue and started to dig around to find the cause of this.

This is just a hypothesis as I didn't dig any further, but maybe it can be some kind of clue. My issue is right here. Please test this again with the latest VS Code insiders build and make sure you are using typescript 3.

April update 1. VSC has been miserably slow since 1.By using our site, you acknowledge that you have read and understand our Cookie PolicyPrivacy Policyand our Terms of Service.

vscode intellisense too slow

Stack Overflow for Teams is a private, secure spot for you and your coworkers to find and share information. I'm using VS Code and it's wonderful is all areas but code completion, where it is usually just too slow to be of any use.

I've not been able to find a solution to this as of yet, so I am here to ask if anyone else has had a similar issue and ask how they have overcome it. It turned out it was a particular VS Code extension for me.

Angular Language Service. Disabling this made it lightning quick. The problem might be with wrong setting configuration. You might want to make sure these setting are on:.

I had the same problem with Python on VS Code. In my case, disabling Jedi for IntelliSence made things faster. As memory is not a problem for me, I also enabled code analysis to keep parser trees in memory: "python.

You will get their list of extensions and their reboot time. Learn more. Ask Question. Asked 1 year, 11 months ago. Active 15 days ago. Viewed 23k times. Anti-Distinctlyminty Anti-Distinctlyminty 1, 2 2 gold badges 12 12 silver badges 20 20 bronze badges. Any solution to this problem?However, since my internet is quite slow when trying to get some of the packages i. I did close VSCode, and managed to get a build going before intellisense tried to update, allowing the build to start, and consequently was able see status messages for libraries and platform stuff being downloaded unpacked… but it is pretty hit and miss… so hopefully there is a better way?

You described everything very well. We need a real toolchain and related frameworks to build configuration for IntelliSense service.

How to Configure Vim like VSCode

It seems that you opened PlatformIO project on a clean machine. Yeah, I was importing projects from another machine via git on a clean install of PlatformIO, so it had the disadvantage of having to download the platform support files, which held things up for a while. It would at least be a stopgap until things could be improved on that front. Hit this problem today too. Yes, it happened after I moved the project to a new machine.

Otherwise, yeah, disabling your networking until you manually run the build would certainly make it behave! It was unexpected for me that a background process like Intellisense index rebuild can install packages.

I thought only Build or Upgrade commands would do it. Perhaps index rebuilding should be made foreground operation with its own terminal? As Ivan pointed out above… for IntelliSense to function, you need. In any case, we will think about how to improve this issue.

As Ivan pointed out above… for IntelliSense to function, you need a real toolchain and related frameworks to build configuration for IntelliSense service.Version 1. Read about the new features and fixes from June. Visual Studio Code's JavaScript IntelliSense provides intelligent code completion, parameter info, references search, and many other advanced language features. While IntelliSense should just work for most JavaScript projects without any configuration, you can make IntelliSense even more useful with JSDoc or by configuring a jsconfig.

When type inference does not provide the desired information, type information may be provided explicitly with JSDoc annotations. This document describes the JSDoc annotations currently supported. In addition to objects, methods, and properties, the JavaScript IntelliSense window also provides basic word completion for the symbols in your file.

IntelliSense for JavaScript libraries and frameworks is powered by TypeScript type declaration typings files.

Optimize Visual Studio performance

Type declaration files are written in TypeScript so they can express the data types of parameters and functions, allowing VS Code to provide a rich IntelliSense experience in a performant manner.

Many popular libraries ship with typings files so you get IntelliSense for them automatically. For libraries that do not include typings, VS Code's Automatic Type Acquisition will automatically install community maintained typings file for you. Automatic type acquisition requires npmjsthe Node.

In this image you can see IntelliSense, including the method signature, parameter info, and the method's documentation for the popular lodash library. Type declaration files are automatically downloaded and managed by Visual Studio Code for packages listed in your project's package. You can alternately explicitly list packages to acquire type declaration files for in a jsconfig.

Most common JavaScript libraries ship with declaration files or have type declaration files available. You can search for a library's type declaration file package using the TypeSearch site. Automatic Type Acquisition uses npmthe Node. To ensure that Automatic Type Acquisition works properly, first ensure that you have npm installed on your machine.

Run npm --version from a terminal or command prompt to quickly check that npm is installed and available. Install the current LTS Long Term Support version and the npm executable will be added by default to your system path. If you have npm installed but still see a warning message, you can explicitly tell VS Code where npm is installed with the typescript.

This should be set to the full path of the npm executable on your machine, and this does not have to match the version of npm you are using to manage packages in your workspace.

The presence of a jsconfig. For common setups, a jsconfig. To define our code as a JavaScript project, create jsconfig.GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together. Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community. Already on GitHub? Sign in to your account. I have seen many other issues here opened about this problem but they all seem to get closed in some way or another.

I cannot be the only one experiencing the broken-ness of Intellisense. I am working in a JavaScript project that is not small on a very strong machine. When I first launch VSC if I let the editor rest a bit perhaps index reading, not sure then Intellisense works very well. After a bit of work in the editor sometimes immediately but often a few minutes of bliss the dreaded loading I can wait from anywhere between 30s and 90s and the window does eventually appear. It's worth saying this is not progressive -- meaning once it goes south it never takes less than 30s.

During this time there are not other large processes running to spike the CPU. This seems to really be within VSC itself. It is also worth noting that there are times when if I let it complete it's loading cycle it starts working at normal speed again for a bit.

This usually does not last long 2m but it does happen. I am willing to get the "intelli" part disabled if at least macros and auto-complete for local values worked. Any way to limit what it was trying to look through to present the feature.

Look through that log file for errors or stack traces. If you can share the log, I can also take a look to see if anything stands out.

Working with JavaScript

If you have any concerns about posting this publicly on Github, just let me know and we can arrange something else.

On our side, we only use these logs to investigate issues like this. Possibly the same issue, but it also hangs when we press F12 Go to definition in our Typescript project. Takes anywhere up to 30s to find. I'm going to try downgrading to 1. For anyone else struggling to find the 1. I'm not sure if this is normal? I can confirm this, however in my project it's files. Here's the complete log file: tsserver. Another thing I've noticed: I have these performance issues in all my Angular projects, however another Node.

Also: All my colleagues experience the same performance issues at least the Windows users. And disabling all extensions didn't help. Following lines always appear in the tsserver. So it should have stopped at line


comments

Leave a Reply

Your email address will not be published. Required fields are marked *