Enabling tracing causes TS Server to crash repeatedly on windows

[sanket-bhalerao]

Type: Bug

typescript server keeps crashing after the latest update VSCODE

I can reproduce this with all the extensions disabled.

LOG:

VS Code version: Code - Insiders 1.76.0-insider (c4a609f, 2023-02-03T05:23:17.202Z)
OS version: Windows_NT x64 10.0.19044
Modes:
Sandboxed: Yes

System Info

Item	Value
CPUs	Intel(R) Core(TM) i7-8665U CPU @ 1.90GHz (8 x 2112)
GPU Status	2d_canvas: enabled canvas_oop_rasterization: disabled_off 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_renderer: enabled_on video_decode: enabled video_encode: enabled vulkan: disabled_off webgl: enabled webgl2: enabled webgpu: disabled_off
Load (avg)	undefined
Memory (System)	15.82GB (4.69GB free)
Process Argv	--crash-reporter-id e5294b27-02c9-4438-b8f3-90acb1091b3b
Screen Reader	no
VM	0%

Extensions (11)

Extension	Author (truncated)	Version
ng-template	Ang	15.1.0
atlascode	atl	3.0.1
vscode-markdownlint	Dav	0.49.0
vscode-eslint	dba	2.2.6
githistory	don	0.6.19
gitlens	eam	13.2.0
prettier-vscode	esb	9.10.4
vscode-yaml	red	1.11.0
sonarlint-vscode	Son	3.14.0
code-spell-checker	str	2.16.0
vscode-stylelint	sty	1.2.3

A/B Experiments

vsliv695:30137379
vsins829:30139715
vsliv368:30146709
vsreu685:30147344
python383:30185418
vspor879:30202332
vspor708:30202333
vspor363:30204092
vstes627:30244334
vslsvsres303:30308271
pythonvspyl392:30422396
pythontb:30258533
vsc_aacf:30263846
pythonptprofiler:30281269
vshan820:30294714
pythondataviewer:30285072
vscod805:30301674
bridge0708:30335490
bridge0723:30353136
cmake_vspar411:30581797
vsaa593:30376534
pythonvs932:30404738
cppdebug:30492333
vscaat:30438846
vsclangdf:30492506
c4g48928:30535728
dsvsc012cf:30540253
pynewext54:30618038
pylantcb52:30590116
pyindex848:30611229
nodejswelcome1:30587009
pyind779:30611226
pythonsymbol12:30651887
showlangstatbar:30657381

[mjbvz]

Please try collecting the TS Server log from the crashed instance:

1. Set "typescript.tsserver.log": "verbose"

2. Restart VS Code and reproduce the problem

3. Open the TypeScript section of the output panel

4. At the very top, find the first line that prints to path to the semantic error log file. It should look something like:

   [Info  - 19:54:59.247] <semantic> Log file: /Users/matb/Library/Application Support/Code - Insiders/logs/20200213T104930/exthost55/vscode.typescript-language-features/tsserver-log-ZT2zau/tsserver.log
   

   That file contains the typescript logs.

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

⚠️Warning: The TypeScript log may include information from your workspace, including file paths and source code. If you have any concerns about posting this publicly on Github, just let me know and we can arrange something else. On our side, we only use these logs to investigate issues like this

[sanket-bhalerao]

@mjbvz , for some reason the log file location is shown as [Object object] (as pointed out by the pink arrow),
I checked in the folder pointed out by the red arrow and the folder is empty.

I have checked this for multiple folder I could see in the log prompt but all of them are empty.

[sanket-bhalerao]

a Microsoft member created same/duplicate issue #173582, in case this could help with the debugging

[nguerrera]

Confirming that I also see [object Object] when using verbose setting and all the log files are empty for me, which is also noted and shown on #173582.

[sanket-bhalerao]

For me the directory under the object object is also empty, is that the case with you?

[nguerrera]

Yes, same.

[mjbvz]

[Object object] should be fixed in the next insider release: #173708

[sanket-bhalerao]

the object object issue is resolved, however, the file pointed by the log still does not exist.
@nguerrera can you give it a try if you can see the logs?

[sanket-bhalerao]

i did some commenting in the settings.json file and found that commenting out "typescript.tsserver.enableTracing": true, setting stops the repeated crash.

Note: I am not sure why I have added/enabled this setting in the first place.