Sean McManus

@AndreKR I just debugged it and I see us calling the VirtualAlloc with MEM_RESERVE with a large value, but small values when MEM_COMMIT is used. You may be able to...

@al20878 If you could get more info via Process Monitor (not process explorer) that could help, in particular logging related to the VirtualAlloc call with the large request. Our current...

@al20878 The workaround should be to set C_Cpp.intelliSenseCacheSize to 0.

@al20878 The cache is not essential and in some cases may hurt performance anyway. The cache writes the compiled header code to a file and memory maps it, but that...

@benj5378 Yes, your issue is different. The original issue is Win 7 specific and repros with any source file and is related to memory mapping with virtual alloc. Your issue...

@HamAndEggs Which process is using CPU/memory? If for some reason our cpptools process doesn't exit right after VS Code shutdown, it should exit after 5 minutes if VS Code is...

This setting seems incorrect -- ` "miDebuggerPath": "/path/to/gdb",` -- are you able to provide a valid value?

@RuoXian233 Do you know the latest version that works? @WardenGnaw Debugging may have regressed on Win7?

Do you intend to format with vcFormat or clangFormat? If you set `files.associations: { "*.frag": "c" }` that should be a workaround, but it would treat the file as C...

You could try setting the C_Cpp.errorSquiggles to "Disabled". You may need to disable other language service features too. However, that would only work if you also don't want those in...