-
Notifications
You must be signed in to change notification settings - Fork 30.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
initializing js/ts language features never completes #68896
Comments
for me the typescript intellisense is not working. |
I'm experiencing this issue since waaaaay longer than today. What does exactly mean "initializing js/ts language features"? What are the features we are talking about? Is it possible to disable these features? What would I miss in case? Any help is deeply appreciated. |
Also having this issue. No extensions installed, no themes. Been experiencing this even after a fresh install. v1.31.1, Windows 10. |
For me the issue resolved after latest update in vsc insiders. |
I've tried latest (bbe40c8) insiders this morning... sadly I can still replicate the problem. After first time I reproduced the issue today, I started a video registration, and then continued to work normally. I was able to see the exact moment in which the error occurs. Apparently I didn't any special, I just cut a piece of JSX from a React component. Just after that I tried to take another recording of a simpler repro, but the surprisingly thing is that now both vscode, and insiders have the issue with whatever javascript files (even with an empty file). I've also restarted my mac, but it was useless. Hope this helps. |
@joshsweaney Could you share a bit more information about the project you are working? JavaScript? Typescript? Perhaps a React application? Thank you. |
Please try checking the TypeScript Server trace:
Are there any errors or stack traces printed near the end? Also, is |
@7cc, Thanks, that helped to reduce the pain. @mjbvz The Thanks for the help so far. |
Thanks. Please sure to test using the latest VS Code insiders build too. I made a small fix yesterday that could have effected this issue |
Hi @mjbvz . I've followed your instructions. I still can reproduce the issue.
Hope it helps. |
After burning hours on this issue, I found cloning my repo into a different folder and opening it there solved the problem. |
same for me :( 1.31.1 |
Always reproducable with freshly installed 1.31.1 in clean Windows 7 Pro 64: Open a file from network location \\server\path_on_server\file.js Does not occur on opening same file on local drive (C:\file.js) or mapped drive S:\path_on_server\file.js Further observations: |
@ojde same for me with this conditions . on local there is no problem but on network drive this message blinking forever ! |
I can reproduce this issue on local repos as well. |
I am running the nightly VS Code build with no external plugins and am seeing this issue on macOS Mojave Version 10.14.3. It has been an issue since late 2018 and it has gotten to the point where I have to use a different IDE. Very sad day because VS Code is my favorite editor of all time. Just unusable at the moment for my javascript purposes. I am subscribing to this thread because I would like to switch back to VS Code when this is resolved. |
@jrlang002 Have you read this comment #68896 (comment)? This didn't fix the issue, but reduced the pain, at least for me. I can understand your frustation; vscode is my favourite editor as well... and like you, I switched back to sublime for a short period. |
... Also it would be nice to have any updates about the state of this issue. Thank you. |
@octref Yes, same in insiders build |
@VadimGorbenko How are you openining |
Not sure this can be verified, and people seem to still have problems, so reopening and moving to April. |
I tried the latest Insider's build you linked to above @octref and I'm still experiencing the same problem. (Although, the link appears to be currently pointing to a different commit.) Version: 1.33.0-insider The output I get seems to indicate VSCode is attempting to access the config file in a location inaccessible to me.
|
@octref ye, my case absolutely the same as sh67 have. With one little difference. I dont drag files into vscode window. I just open whole folder with "Open folder" function and paste path to this library. Node -v : 8.10.0 |
I removed the |
I am the same as @sh67 I am opening a SiteAssets folder using a mapped drive and it's causing 100% usage. I am using open workspace instead of solder. |
same. on all recent (couple of months?) normal and insider builds. |
Sounds like the remaining issues are for windows network drives. I can't repo this when using a drive mapped to localhost, or a simple mapped from sharepoint either (although I do see a slowdown as you'd expect in this case) For people still hitting this:
|
@mjbvz I'll try to answer your questions for my case, and I want to add a couple of points I discovered this morning.
If I actually map the folder (SiteAssets for me) to a Windows drive letter, like Z:, and then drag the file from the Windows Explorer window onto the open VSCode window, I do not encounter the problem. If I use the 'Open folder ...' command from the 'File' menu in VSCode to open the folder, even without the drive letter mapping in place, and then click on the file in the VSCode Explorer pane, I do not encounter the problem. I'm still using the same build as the one I referred to in my original reply. |
Seeing this behavior on macOS Version 1.33.0 (1.33.0). Just trying to open my No |
@joshuaiz Please open a new issue |
Same on my side macOS Version 1.33.0 As a side note, it'll be great if VS Code would provide clear separation of TS from JS e.g. I'm totally not interested in TS integration (would love to have that off) and returning bugs (related to TS support) make me ineffective with VS Code. |
Still having this problem. |
Still getting this constantly. I already opened #71109 and had it closed as a duplicate. |
Steps to Reproduce:
write code, open multiple files, switching between files, write code...
and then, apparently without any particular reason the error occurs.
Does this issue occur when all extensions are disabled?: Yes. I've tried.
I know these are not the best steps to reproduce in the world,
but I was not able to identify a common pattern in the errors,
also cause I don't immediately notice the error, until I need to toggle a region.
After the error occurs the editor is almost completely frozen.
I can edit the code, but I cannot open/close regions of code.
The only way to restore functionalities is to close/reopen vscode.
This is happened at least 5 times to me only in the last hour.
The text was updated successfully, but these errors were encountered: