TS functionality keeps dying on large project #44951
Comments
|
(Experimental duplicate detection) |
|
Does this reproduce in the latest VS Code insiders build with all extensions disabled? |
|
I have the latest version 1.56.2 .. will disable all extensions and give it a try |
|
Please test using the insiders version: 1.57 |
|
I've just tried insiders version 1.57, with no extensions installed, fyi, may be I started experiencing this heavily this week only .. don't remember exactly when though! |
|
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
|
|
Well, TSServer keeps exiting periodically with rolling over to a new log file each time as follows: Typescript OutputThe very first log file didn't have any The 2nd log file, kept showing this Errorand of course the I checked 2 random remaining files, but they didn't have any Let's also notice that this whole case happens when my RAM is full or near full I really hope this would help .. and thanks a lot for following up on this |
|
Hm, do you see this for every project you open or just one of them in particular? I'm going to add some extra logging to also see if some kind of out of memory issue is causing this |
|
The next insiders build will also log the exit signal for the server process. Hopefully that helps us track down what is going on |
|
About your question .. I'm working only on one Typescript project (backend one) for quite a while now .. so, I can't tell if other Typescript projects would work well or not .. but other javascript projects are working fine with me though. |
|
Did you have a chance to test using the most recent insiders build? It should print more info when the server exits |
|
Sorry for being late, well, in a single log file, I can see about 15 occurrences for loading the global Plugin loading partAbout the The first file named and the one after it called |
|
Is this a very large project? |
|
Yes it is a very large project indeed, and we are separating it into different packages with utilizing project references as recommended, I tried to increase the I could have increased it more than that, but I have only 16 GB, and I still need Docker and browser and other stuff, where it might not be practical to increase it more than that I guess. |
|
Can you also try some of the recommendation listed in https://code.visualstudio.com/docs/typescript/typescript-compiling#_working-with-large-projects Transferring to TS for further investigation about why it may be using so much memory |
mjbvz
changed the title
RyanCavanaugh
added
the
Needs More Info
|
I noticed also something .. even with the default Opening one JS file, no matter how small it is, it will make it highly likely for VSCode to have this issue. |
|
I was having this very similar issue in a remote devcontainer setup with docker on a somewhat larger project. I changed this setting |
|
I am having the same issue with a large monorepo that I am working in. For context, our root tsconfig.json has about 110 references. I have tried opening the project in the latest insider build with no extensions and see the same thing. When I opened it in insiders I did get a macOS crash report for an electron SIGABRT. I can send it to possibly @RyanCavanaugh. System InfoVersion: 1.66.0-insider (Universal) Commit: db0525f Date: 2022-03-17T05:18:05.656Z Electron: 17.1.1 Chromium: 98.0.4758.109 Node.js: 16.13.0 V8: 9.8.177.11-electron.0 OS: Darwin arm64 21.4.0 |
|
Same issue here with a very large project. I have the same issue @Abdelhady has, when I open a JS file it increases the chance of the infinite TS server restarting to occur. |
|
Same issue here, typescript goes out of memory on a multi package monorepo. |
|
I stumped on this problem and I believe the root cause is here: microsoft/vscode#127105 It has nothing to do with TypeScript but rather vscode is running tsserver with an inherent memory from electron and it cannot be changed 😠 |
Why is this issue still open if the problem is just the vscode and not the ts itself, lol |
|
We implemented microsoft/vscode#191019 so you can now run tsserver under |
Issue Type: Bug
VSCode keeps trying to "Initializing JS/TS language features", but fails consistently
I'm working on a large backend typescript project in Amazon though
VS Code version: Code 1.56.2 (054a9295330880ed74ceaedda236253b4f39a335, 2021-05-12T17:44:30.902Z)
OS version: Darwin x64 19.6.0
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
Extensions (8)
A/B Experiments
The text was updated successfully, but these errors were encountered: