vscode: [1.40] The TypeScript language service died 5 times right after it got started. The service will not be restarted
Version: 1.40.0 Commit: 86405ea23e3937316009fc27c9361deee66ffbf5 Date: 2019-11-06T17:09:34.601Z Electron: 6.1.2 Chrome: 76.0.3809.146 Node.js: 12.4.0 V8: 7.6.303.31-electron.0 OS: Darwin x64 18.7.0
Steps to Reproduce:
- Open a file.
- Get message
The TypeScript language service died 5 times right after it got started. The service will not be restarted.
- Click “Report Issue”
- Get message
The TypeScript language service died 5 times right after it got started. The service will not be restarted.
- STOP RESTARTING IT THEN
- Save a file
- Get message
You have legacy options in your VS Code settings. They are being ignored. Would you like to migrate them to '.prettierrc', remove them, or view the logs?.
- Click “Migrate Settings” and create new
.prettierrc
file in directory - Save file again later
- Get message
You have legacy options in your VS Code settings. They are being ignored. Would you like to migrate them to '.prettierrc', remove them, or view the logs?.
- This time, click “Remove Settings”
- Save file again later
- Get message
You have legacy options in your VS Code settings. They are being ignored. Would you like to migrate them to '.prettierrc', remove them, or view the logs?.
- Please leave me alone.
I’m seeing a lot of other issues around this version as well. This is a critical piece of software for many developers. Bugs like this shouldn’t make it to a release.
About this issue
- Original URL
- State: closed
- Created 5 years ago
- Reactions: 5
- Comments: 33 (8 by maintainers)
+1 This bug ruins the whole experience of using vscode and I get the error all the time. Plus it makes the editor slower and intellisense stops working.
That part about:
I got it in 1.40 insiders and even in stable 1.40 once or twice. How I couldn’t say. I thought the problem was JS/TS nightly extension, but after deleting it the problem was still there.
Downgrading to version 1.39 until it’s fixed
On Mon, Dec 2, 2019, 17:29 dudeinco notifications@github.com wrote:
I had it as well in 1.40, 1.40.1, 1.40.2. I have tried TypeScript 3.7.3, also no effect.
Oh yes, I am getting an INSANE amount of these. It seems to especially happen when you tab on a class that isn’t imported in a TS file yet (auto import) - when you do this, it kills the line you’re working on, and doesn’t add the import at the top of the file.
After this happens (I’m running NG serve in the terminal below), it starts saving the file on every keypress - I believe that’s what it’s doing, because if you watch the output, errors pop up below in the terminal, every time you hit a key. Very frustrating, every annoying. Rebooting/restarting doesn’t appear to solve the issue. W10
Edit: It looks like the only way to stop the constant autosaving on each key press is to close the file, and reopen it.
Edit 2: It also appears that hitting ‘enter’ instead of ‘tab’ for completion seems to help? Appears to be at the moment, but purely speculative.
Updating to 3.7.3 hasn’t helped for me, still getting “The TypeScript language service died 5 times right after it got started.” Downgrading VS Code to 1.39 seems to have fixed it. EDIT: Spoke too soon, downgrading hasn’t helped either 😦
Same problem here as @dudeinco with constant recompilation every keypress! Disabling all plugins didn’t fix it. Reverting to 1.39 did it - thanks @PaunCostin https://code.visualstudio.com/updates/v1_39
I don’t have GitLens but the problem occurs all the time.
I have tested without more extensions and the problem seems to disappear when I disabled Git Lens. Try it!
EDIT: Been able to work the whole day without getting the message with Git Lens disabled. Though I miss it. Heading over there to see if they have a fix!
I’m actually not even using typescript (but it seems to be the same service for both javascript and ts) so I got whatever shipped with VS Code 1.40.2 which seems to be 3.6.3 atm.
Thanks. Closing this as a possible duplicate of https://github.com/microsoft/TypeScript/issues/35094 or https://github.com/microsoft/TypeScript/issues/35001
Let me know if you see this in the next VS Code insiders build (the next one should have a new version of TypeScript 3.7.3-insiders that has a fix)