TS Server fatal error: Debug Failure. #60243
Comments
|
Thanks for creating this issue! It looks like you may be using an old version of VS Code, the latest stable release is 1.94.2. Please try upgrading to the latest version and checking whether this issue remains. Happy Coding! |
|
Hi, I just updated to the version mentioned and I am still facing this issue. To get Typescript to work again, I am forced to close VS Code and reopen it. Restarting the TS server does nothing. Version: 1.94.2 (Universal) |
|
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
|
|
Here's the error logs I found. I hope this helps Typescript Outputtsserver.logFrom another tsserver.log |
|
@MerryCello can you share a full TS Server log (not just the error stack)? Are you able to reproduce this consistently with specific steps, or does it seem to stop working randomly? |
|
Sure, I can provide that. I can't pinpoint what triggers it. It just
happens randomly (every 30-1hr of usage).
…On Thu, Oct 17, 2024, 15:01 Andrew Branch ***@***.***> wrote:
@MerryCello <https://github.com/MerryCello> can you share a full TS
Server log (not just the error stack)? Are you able to reproduce this
consistently with specific steps, or does it seem to stop working randomly?
—
Reply to this email directly, view it on GitHub
<#60243 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AIYCXDV2EIDHTCPXGBE7QLTZ4AJQVAVCNFSM6AAAAABQB32AM6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIMRQGQYTMMRVGA>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
|
I was able to capture a full log (v1.94.2). This was with a fairly big open-source repo. Although it happened several times, I'm not able to reproduce it. If I find a way, I will post it here. |
|
I've also been struggling with these errors for the past couple weeks. I'm also not sure what triggers it but it typically happens to me about every 10 - 30 minutes. |
|
This error is making vscode pretty un-usable now. |
|
with the current vscode version: 1.95.3, I grabbed the maybe in any case, I did {
"resolvedModule": {
"resolvedFileName": "/app/node_modules/moment/ts3.1-typings/moment.d.ts",
"extension": ".d.ts",
"isExternalLibraryImport": true,
"packageId": {
"name": "moment",
"subModuleName": "ts3.1-typings/moment.d.ts",
"version": "2.29.4"
},
"resolvedUsingTsExtension": false
},
"failedLookupLocations": [
"/app/node_modules/moment-timezone/node_modules/moment/package.json",
"/app/node_modules/moment-timezone/node_modules/moment.ts",
"/app/node_modules/moment-timezone/node_modules/moment.tsx",
"/app/node_modules/moment-timezone/node_modules/moment.d.ts",
"/app/node_modules/moment-timezone/node_modules/moment/index.ts",
"/app/node_modules/moment-timezone/node_modules/moment/index.tsx",
"/app/node_modules/moment-timezone/node_modules/moment/index.d.ts",
"/app/node_modules/moment-timezone/node_modules/@types/moment/package.json",
"/app/node_modules/moment-timezone/node_modules/@types/moment.d.ts",
"/app/node_modules/moment-timezone/node_modules/@types/moment/index.d.ts",
"/app/node_modules/moment.ts",
"/app/node_modules/moment.tsx",
"/app/node_modules/moment.d.ts"
],
"affectingLocations": [
"/app/node_modules/moment-timezone/package.json",
"/app/node_modules/moment/package.json",
"/app/node_modules/moment-timezone/package.json"
]
} |
|
It would be good to know if #60039 resolves this issue. Could any of you test it out using a build from that branch? |
I can try - but ... Is there an easy way to install that branch to be used with vscode? |
|
@jerry2013 a fresh PR build is available here: #60039 (comment) |
|
I found a repro for this in the TypeScript repo.
|
|
#60039 does not fix it, so I’ll investigate |
|
@MerryCello @jerry2013 I think I’m narrowing in on a root cause but there might be multiple. Do you have any import type pkg from "pkg" with { "resolution-mode": "import" } |
|
@andrewbranch the JS project that I experience the tsserver crash problem has |
|
@jerry2013 what version of each? Are you able to share the project you work on? If not, I may make a patch you can apply to make TS spit out an extra log to narrow down what’s going on. It sounds like you have a different root cause than I do. |
|
Can folks try out the build at #60910 (comment)? |
Type: Bug
❗️❗️❗️ Please fill in the sections below to help us diagnose the issue ❗️❗️❗️
TypeScript Version: 5.6.2
Steps to reproduce crash
I didn't do anything difference as last time I opened VS Code and now it's crashing
After regular usage, the TS server will just freeze up (infinite loading & no editing helpers).
According to issue Initellisense infinite loading microsoft/vscode#52691, I should be able to fix this by increasing TS server's memory, but I shouldn't have to do that...
TS Server Log
❗️ Server logging disabled. To help us fix crashes like this, please enable logging by setting:
After enabling this setting, future crash reports will include the server log.
VS Code version: Code 1.94.0 (Universal) (d78a74bcdfad14d5d3b1b782f87255d802b57511, 2024-10-02T13:08:12.626Z)
OS version: Darwin arm64 23.6.0
Modes:
System Info
canvas_oop_rasterization: enabled_on
direct_rendering_display_compositor: disabled_off_ok
gpu_compositing: enabled
multiple_raster_threads: enabled_on
opengl: enabled_on
rasterization: enabled
raw_draw: disabled_off_ok
skia_graphite: disabled_off
video_decode: enabled
video_encode: enabled
webgl: enabled
webgl2: enabled
webgpu: enabled
webnn: disabled_off
Extensions (14)
A/B Experiments
The text was updated successfully, but these errors were encountered: