v0.20260119.1 crashes ts server for large project, v0.20260116.1 works

[austinfennacy]

Stack trace

// Cursor > Output > typescript-native-preview doesn't show any errors, but the server becomes unresponsive

Steps to reproduce

1. have a large repository that requires at least "typescript.tsserver.maxTsServerMemory": 8000, for the server to run
2. install TypeScript (Native Preview) extension v0.20260119.1
3. in Cursor & VS Code, server will initialize but becomes unresponsive / crashes

to capture the issue better I recorded a zoom clip:

https://front.zoom.us/clips/share/_6gXTMSEQM66OqGNqp0Dow
Passcode: e^8g2t5K

for now I'll be sticking with v0.20260116.1

[DanielRosenwasser]

It's possible that this is a regression from #2499 and #2568 might have fixed this. 0.20260122.4 was published an hour ago, so would you be able to give that a shot?

[Titozzz]

Just FYI we also noticed that since 3-4 days, and team members have either rolled back to a previous version or disabled tsgo. Someone noticed RAM usage up to 40 Go from the server!

[kratos-respawned]

Just FYI we also noticed that since 3-4 days, and team members have either rolled back to a previous version or disabled tsgo. Someone noticed RAM usage up to 40 Go from the server!

Yeah, I noticed the same. My memory usage for the language server went to 92GB.

[Titozzz]

Seems like 0.20260122.4 is better, will report if issue rises again

[austinfennacy]

Seems like 0.20260122.4 is better, will report if issue rises again

agreed!

my setup usually had tsgo memory usage of 6-7GB on Jan 16th version and before, Jan 19th version completely crashed, and Jan 22nd version works again. When testing Jan 22nd the first time my tsgo memory shot up to 9-10GB, but when I tried to reproduce this for a zoom clip using Jan 22nd memory remained between 6-7GB. I'm not sure if fluctuations like this are expected behavior, or if a recent change introduced memory issues.

https://front.zoom.us/clips/share/IQtumkg3Rtiz0DetAMNEyw
Passcode: e@1%?6ug

Anyhow I'll stay pinned to 0.20260122.4 for now. (edit - I'll keep auto-update enabled)

while what I identified as my original issue has been resolved (v0.20260119.1 crashes), other users brought up increased memory usage. it's unclear to me if that was a 1-off issue with v0.20260119.1, or if 0.20260122.4 also has memory issues, so I'll leave this issue open and give the tsgo team discretion to close it. I don't know enough to test & determine if the latest releases definitively have memory issues.

[DanielRosenwasser]

It looks like we've solved this issue (caused by a very subtle regression) and #2553 fixes a memory leak that's been around for at least the last month the last few weeks. Maybe it's good to know that 0.20260122.4 is a decent last-known-good version, but I would ask that nobody specifically pin to one version of the extension. We really do appreciate hearing if things start going wrong, and it's easy enough to pin after the fact.