"Connection to server got closed. Server will not be restarted." after update to 0.26.3insiderX

[jwierzbi]

Issue Type: Bug

Hard for me to say what are the reproduction steps for this issue. It just happens when I have a C project opened. The message pops up periodically every few minutes.

This specifically appears after updating to 0.26.3. I had an 0.26.3-insiders version before and I reverted it to 0.26.2 and the error was gone. Now I updated again because the insiders2 version rolled out and the error is back.

I know there's already #4714 but it was raised against an earlier version which I had no problems with so this might be a different issue.

Extension version: 0.26.3-insiders2
VS Code version: Code 1.41.0 (9579eda04fdb3a9bba2750f15193e5fafe16b959, 2019-12-11T18:32:17.711Z)
OS version: Linux x64 4.15.0-73-generic

System Info

Item	Value
CPUs	Intel(R) Core(TM) i7-3770 CPU @ 3.40GHz (8 x 2948)
GPU Status	2d_canvas: enabled flash_3d: enabled flash_stage3d: enabled flash_stage3d_baseline: enabled gpu_compositing: enabled metal: disabled_off multiple_raster_threads: enabled_on oop_rasterization: disabled_off protected_video_decode: unavailable_off rasterization: disabled_software skia_renderer: disabled_off surface_control: disabled_off surface_synchronization: enabled_on video_decode: unavailable_off viz_display_compositor: enabled_on viz_hit_test_surface_layer: disabled_off webgl: enabled webgl2: enabled
Load (avg)	2, 2, 2
Memory (System)	15.54GB (1.08GB free)
Process Argv	--unity-launch
Screen Reader	no
VM	0%

Note: The memory above shows that I have 1.08GB free but it's actually more. I'm on Linux and most of the memory is taken by caches. The actual value for free is around 10GB.

[sean-mcmanus]

The crash we fixed with 0.26.3-insiders2 was with the IntelliSense process, but you're hitting a main process crash. We aren't aware of any high hitting main process crash, except for an out of memory crash on Windows -- does it appear like the process keeps growing memory usage till it runs out?

Doing a Reset IntelliSense Database might fix things if the database is corrupt in some way.

Can you attach a debugger before the process crashes to get a call stack?

[jwierzbi]

does it appear like the process keeps growing memory usage till it runs out?

I haven't noticed anything out of the ordinary regarding memory usage in my system when this issue happens.

Doing a Reset IntelliSense Database might fix things if the database is corrupt in some way.

Tried twice and sadly I can still see the error message.

Can you attach a debugger before the process crashes to get a call stack?

I'm not overly familiar with debugging Electron apps but I dumped the developer tools' console (attached). Hope that helps but if it's not enough I'll try and figure out how to fire up the debugger later.

vscode_console.log

[jwierzbi]

I attached GDB to the Microsoft.VSCode.CPP.Extension.linux process and this is the stack trace from the crash: vscode_bt.log.

[saidganim]

Having the same issue here. Last night I updated the VSCode C/C++ IntelliSense cpptools and then started getting the "Connection to server got closed. Server will not be restarted." message periodically with my C project.

[sean-mcmanus]

@jwierzbi Thanks a lot for providing that call stack -- that looks like our top hitting main process crash, and it's a regression with 0.26.3-insiders2, but it was below our "crash bar threshold", so we had not investigated it further yet.

But now that it's been user reported we'll try to dig into it next week :)

@saidganim Are you on 0.26.3-insiders2?