Skip to content

On Windows cpptools.exe is 32-bit and running out of memory in large workspace #7230

Closed

Description

Type: LanguageService

Describe the bug

  • OS and Version:
  • VS Code Version:
  • C/C++ Extension Version:
  • 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

  1. Run vscode-cpptools on a large workspace such as Chromium.
  2. Intellisense doesn't work as cpptools.exe crashes.

Expected behavior

Logs
Insert logs here.

Screenshots

Additional context

Activity

  1. sean-mcmanus commented on Mar 25, 2021

    @sean-mcmanus
    Contributor

    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?

  2. sean-mcmanus commented on Apr 1, 2021

    @sean-mcmanus
    Contributor

    It sounds like we have an internal repro we could try.

  3. ghost closed this as completedon Jan 26, 2022
  4. ghost reopened this on Jan 26, 2022
  5. ghost closed this as completedon Jan 26, 2022
  6. locked and limited conversation to collaborators on Mar 12, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

Language ServicebugfixedCheck the Milestone for the release in which the fix is or will be available.performance

Type

No type

Projects

No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions