microsoft / microsoft/TypeScript
TS Server fatal error: Maximum call stack size exceeded
Open
@iisaduan is already working on this.
Since Jul 12, 2024.
Bug
Domain: Crashes
Needs Human Review
Needs More Info
- Dominant language
- Go
- Stars
- 111k
- Forks
- 14.3k
- Avg merge
- 1d 19h
- Merged PRs (30d)
- 117
Description
Type: Bug
❗️❗️❗️ Please fill in the sections below to help us diagnose the issue ❗️❗️❗️
TypeScript Version: 5.4.5
Steps to reproduce crash
1.打开我创建的包含语法错误的文件
TS Server Log
❗️ Server logging disabled. To help us fix crashes like this, please enable logging by setting:
"typescript.tsserver.log": "verbose"
After enabling this setting, future crash reports will include the server log.
VS Code version: Code 1.88.1 (e170252f762678dec6ca2cc69aba1570769a5d39, 2024-04-10T17:41:02.734Z)
OS version: Windows_NT x64 10.0.22000
Modes:
System Info
| Item | Value |
|---|---|
| CPUs | Intel(R) Core(TM) i7-1065G7 CPU @ 1.30GHz (8 x 1498) |
| GPU Status | 2d_canvas: enabled 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 vulkan: disabled_off webgl: enabled webgl2: enabled webgpu: enabled |
| Load (avg) | undefined |
| Memory (System) | 15.69GB (9.04GB free) |
| Process Argv | --crash-reporter-id 4f95837e-4e0c-461e-a6cd-fcd03dcca8e7 |
| Screen Reader | no |
| VM | 25% |
Extensions (11)
| Extension | Author (truncated) | Version |
|---|---|---|
| masm | bli | 0.0.5 |
| githd | hui | 2.3.5 |
| vscode-wasm-syntax-lite | jcm | 0.3.0 |
| vscode-language-pack-zh-hans | MS- | 1.88.2024041009 |
| remote-wsl | ms- | 0.88.0 |
| hexeditor | ms- | 1.9.14 |
| webgl-glsl-editor | rac | 1.3.8 |
| vscode-yaml | red | 1.14.0 |
| qf | Wsc | 6.8.122 |
| vue | Wsc | 1.0.26 |
| markdown-all-in-one | yzh | 3.6.2 |
A/B Experiments
vsliv368cf:30146710
vspor879:30202332
vspor708:30202333
vspor363:30204092
vscorecescf:30445987
vscod805cf:30301675
binariesv615:30325510
vsaa593:30376534
py29gd2263:30899288
c4g48928:30535728
azure-dev_surveyone:30548225
a9j8j154:30646983
962ge761:30959799
pythongtdpath:30769146
pythonidxpt:30866567
pythonnoceb:30805159
asynctok:30898717
pythontestfixt:30902429
pythonregdiag2:30936856
pyreplss1:30897532
pythonmypyd1:30879173
pythoncet0:30885854
h48ei257:31000450
pythontbext0:30879054
dsvsc016:30899300
dsvsc017:30899301
dsvsc018:30899302
cppperfnew:31000557
d34g3935:30971562
fegfb526:30981948
bg6jg535:30979843
ccp2r3:30993541
dsvsc020:30976470
pythonait:31006305
gee8j676:31009558
dsvsc021:30996838
g1icg217:30999571
945dj816:31013170
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.