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
The TypeScript language service died 5 times right after it got started. The service will not be restarted. #133048
Comments
Log
|
Does this reproduce in the latest VS Code insiders build with all extensions disabled? If so, please try collecting the TS Server log from the crashed instance:
Look through that log file for the first error or stack trace you see. If you can share the log, I can also take a look to see if anything stands out
|
I've been running into something a little like this. Specifically when coding on https://github.com/elastic/kibana over a Remote-SSH connection. I'll set |
One thing I noticed initially is that I seem to have two tsserver.js instances running:
Is this expected? |
@matschaffer Yes it is expected. If you are seeing crashes, please follow the steps to collect the logs and then open a new issue with them so we can investigate |
Will do! I turned them on, restarted both vscode and killed the remote ssh server. Will post if/when I see it happen again with logs in hand this time. I don't think removing all extensions is feasible since I can't effectively use vscode for work without the extensions. At very least I'd need typescript, prettier and remote-ssh. I could possibly trim it down to just that. |
Hey @mjbvz it finally happened at the end of the day. I have the log but it's 4GB (220MB zipped). Is there a microsoft upload server I could put them on for you? |
It just happened to me, check if this isn't your issue: #133515 |
Thanks @jakub-g ! I haven't been editing any non-TS, but I wonder if maybe some bad syntax in TS could have caused this? The other thing maybe worth noting is that I'm using VSCode to work on https://github.com/elastic/kibana which is I hear is ~2.5MM lines of TS at this point. I wonder if maybe I'm hitting some resource contention issues. |
Closing as we need logs/steps to reproduce from the original poster |
Issue Type: Bug
Was just working on some JS when my intelliSense died. I restarted VS Code and it didn't last 2 minutes before dying again. Tried it on VS Code Insiders and it did the same thing.
I don't really know how to reproduce it since I was just doing normal JS things and using an node.js CLI tool
VS Code version: Code 1.60.0 (e7d7e9a, 2021-09-01T10:54:53.442Z)
OS version: Darwin x64 21.1.0
Restricted Mode: No
System Info
gpu_compositing: enabled
metal: disabled_off
multiple_raster_threads: enabled_on
oop_rasterization: enabled
opengl: enabled_on
rasterization: enabled
skia_renderer: disabled_off_ok
video_decode: enabled
webgl: enabled
webgl2: enabled
macOS Version: 12.0 (Monterey) Beta (21A5506j)
VS Code Version:
Version: 1.60.0 Commit: e7d7e9a9348e6a8cc8c03f877d39cb72e5dfb1ff Date: 2021-09-01T10:54:53.442Z (1 wk ago) Electron: 13.1.8 Chrome: 91.0.4472.164 Node.js: 14.16.0 V8: 9.1.269.39-electron.0 OS: Darwin x64 21.1.0
Extensions (84)
(5 theme extensions excluded)
A/B Experiments
The text was updated successfully, but these errors were encountered: