You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
On Windows cpptools.exe is 32-bit and running out of memory in large workspace #7230
Other extensions you installed (and if the issue persists after disabling them):
Does this issue involve using SSH remote to run the extension on a remote machine?:
A clear and concise description of what the bug is, including information about the workspace (i.e. is the workspace a single project or multiple projects, size of the project, etc).
I'm trying to work with Intellisense in a ~1.5m file workspace with compile_commands.json, which was working before. As of 1.22, it is broken for me. Upon further investigation I see that the cpptools.exe is crashing after going over 4 GB because it's 32-bit process even though I'm running 64-bit VSCode.
Steps to reproduce
Run vscode-cpptools on a large workspace such as Chromium.
Intellisense doesn't work as cpptools.exe crashes.
Our 1.3.0 release is expected to have a change that should reduce memory and processing time for really large workspace (the change isn't in 1.3.0-insiders or 1.3.0-insiders2 yet).
We've tested with chromium previously and didn't get any out of memories. Could you provide more repro details?
Activity
sean-mcmanus commentedon Mar 25, 2021
Do you know what version worked for you? Did you want us to use less memory or provide a 64-bit vsix for 1.2.2? The last 64-bit vsix we made available is with 1.1.0 at https://download.visualstudio.microsoft.com/download/pr/17062e60-bd73-48b7-bc31-54d71ef5d48d/2895a0d0eda48a734f6575e103524c42/cpptools-win64.vsix . We don't normally publish a 64-bit vsix because we don't expect our users to need to use that much memory.
Our 1.3.0 release is expected to have a change that should reduce memory and processing time for really large workspace (the change isn't in 1.3.0-insiders or 1.3.0-insiders2 yet).
We've tested with chromium previously and didn't get any out of memories. Could you provide more repro details?
sean-mcmanus commentedon Apr 1, 2021
It sounds like we have an internal repro we could try.