The TypeScript language service died unexpectedly 5 times in the last 5 Minutes. #95122
Assignees
Labels
info-needed
Issue requires more information from poster
Comments
|
I have tried also this: https://marketplace.visualstudio.com/items?itemName=ms-vscode.vscode-typescript-next and no success. |
|
Are you using your own version of TypeScript in the workspace? Also when this happens, there should be a report issue button the shows up. When you click that, it includes the full call stack of the crash. Please share that |
I have tried both the "VS Code's version 3.8.3" and "workspace version 3.8.3". It didn't work.
I'm not sure if this is what you requested above, so: Steps to reproduce: Open a TS file, press Ctrl+Click(left) or mouse hover on a class name in order to navigate to its definition. System info:
Extensions:
|
|
Thanks for testing. I'm looking for the crash stack. When a crash happens in VS Code, you should see a notification that says, If this doesn't work, then try running the |
I've tried several times but I can't see any more info in the pop-up, opened by the IDE, than what I send you in the tables above, maybe I do something incorectly. Here are the log errors: |
|
Where those the first typeScript errors from the log? |
|
Yes, they are! I have filtered only for errors but If you consider useful I can send you also the warnings. |
|
Here they are all logs(this time I opened a ".js" file): |
|
I see that there si no solution, I rollback to v1.39.2, at least that one works and do not make my laptop fun to take fire as the next versions do when they throw the typescript error. |
mjbvz
added a commit
that referenced
this issue
Apr 22, 2020
|
I would like to add one more thing, maybe it helps. I see that only some nodejs projects are behaving like that, others not. Is there any config file that could be the issue? Thanks! |
|
Hey @mjbvz, this issue might need further attention. @SurrenderToTheNow, you can help us out by closing this issue if the problem no longer exists, or adding more information. |
|
Closing this issue as out of date If you are still seeing it in VS Code 1.48+, please open a new issue |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Ubuntu 19.10
Version: 1.44.0
Commit: 2aae1f2
Date: 2020-04-08T11:22:13.689Z
Electron: 7.1.11
Chrome: 78.0.3904.130
Node.js: 12.8.1
V8: 7.8.279.23-electron.0
OS: Linux x64 5.3.0-45-generic
I've tried to use intellisense inside js/ts files. This issue persists from the moment I've installed Ubuntu 19.10 in october 2019. From my point of view there is a compatibility issue. The only way to make intellisense to work just enough(js files will not work) is to downgrade to version 1.39.
The text was updated successfully, but these errors were encountered: