Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Memory "leak" when parsing a large workspace #2737

Closed
sean-mcmanus opened this issue Oct 30, 2018 · 2 comments
Closed

Memory "leak" when parsing a large workspace #2737

sean-mcmanus opened this issue Oct 30, 2018 · 2 comments
Labels
bug fixed Check the Milestone for the release in which the fix is or will be available. Language Service performance reliability
Milestone

Comments

@sean-mcmanus
Copy link
Contributor

sean-mcmanus commented Oct 30, 2018

  1. Open a large workspace such as chromium with >100k files to parse. The issue occurs the 1st time or after a Reset IntelliSense Database occurs.

Bug: Memory usage of the main process keeps increasing. It's possible we could crash from an out of memory on 32-bit Linux.

UPDATE: Actually, looks like our parser is accumulating memory in various places (i.e. not a simple fix). The workaround is to do a Reload Window if memory usage gets too high.

UPDATE: Should be fixed with 0.21.0-insiders (auto installed if "C_Cpp.updateChannel": "Insiders" is set, or manually installed from the offline vsix). Let us know if you find any problems with it.

@sean-mcmanus sean-mcmanus added this to the November 2018 milestone Oct 30, 2018
@sean-mcmanus sean-mcmanus modified the milestones: November 2018, Triage Oct 30, 2018
@sean-mcmanus sean-mcmanus modified the milestones: Triage, December 2018 Nov 8, 2018
@sean-mcmanus sean-mcmanus added the fixed Check the Milestone for the release in which the fix is or will be available. label Nov 8, 2018
@chraac
Copy link

chraac commented Nov 28, 2018

I found similar problem when in 0.20.1, and it create plenty of powershell process.

@bobbrow
Copy link
Member

bobbrow commented Nov 28, 2018

The powershell process issue is a bug in the telemetry package we depend on. See #2822. A fix is committed to our repo, but you'll want to downgrade to 0.20.0 (and disable automatic updates) until we publish a version with that fix.

@github-actions github-actions bot locked and limited conversation to collaborators Oct 11, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug fixed Check the Milestone for the release in which the fix is or will be available. Language Service performance reliability
Projects
None yet
Development

No branches or pull requests

3 participants