Type: LanguageService
Describe the bug
After updating to 0.26.0 a message pops-up that the language-server crashed more than 5 times the last 3 minutes and will not restarted anymore.
To Reproduce
It should be reproducible by simply installing 0.26.0
Expected behavior
I would simply expect it to not crash the language server
Screenshots
Additional context
[Error - 09:35:47] Connection to server got closed. Server will not be restarted.
Confirm same issue here, on Fedora 30 after updating to 0.26.0.
For now switched back to 0.25.1 as a workaround.
I am also getting the same error today now switched back to the previous version 0.25.1 and disable auto-update extensions because of this.
I have the same problem (Windows 10)
Same for Ubuntu 16.04
We are seeing crashes with the document outline in our telemetry that we didn't see in our testing. We have removed the release for now while we investigate the issue. We're sorry about the disruption this has caused!
You can revert back to 0.25.1 by changing the "C_Cpp.updateChannel" setting to "Default". You shouldn't need to disable auto-update of all extensions for this.
We found a repro and are preparing a fix.
I think I'm seeing this issue in 0.26.0-insiders2 release. Microsoft.VSCode.CPP.IntelliSense.Msvc.exe process is crashing frequently (in Process Explorer I can see that there are few instances started and dying one by one, sometimes one or two survives a bit longer).
Procdump reports following exception: Exception: E06D7363.?AUa_cfe_exception@@.
Should I report this as new issue?
@sean-mcmanus I too am still seeing this issue in 0.26.0-insiders2 on Ubuntu 16.04. Additionally, my computer seems to freeze momentarily when VS Code is open with this configuration.
It turns out to be memory related (https://github.com/microsoft/vscode-cpptools/issues/4386)

It just keeps consuming all ram, crashing and then restarting to do the same
@Novakov Your issue with the IntelliSense process crashing is different from the other issues. We need more info as to what is causing the crash and/or a call stack. We are not aware of any new regression involving the IntelliSense process, but we do have a fix pending for our next release for a high hitting IntelliSense crash, see https://github.com/microsoft/vscode-cpptools/issues/4302 .
@sean-mcmanus OK, thanks for the link. I will try to reproduce my issue in more controlled manner and create new issue if it will be unrelated to the one you metioned.