VSCode memory leak issue marked “out-of-scope”

Re:VSCode memory leak issue marked “out-of-scope” by brundolf on Tuesday November 24, 2020 @12:28AM (#25195580)

I have heard of people running into issues with the file-search indexer taking a long time on extraordinarily large projects. The largest project I've used it on was in the thousands of files (excluding node_modules) and didn't have any issues. But I know there are much larger projects out there, so I can't speak to those.

[ Parent | on HN ]

Re:VSCode memory leak issue marked “out-of-scope” by ogre_codes on Tuesday November 24, 2020 @12:40AM (#25195639)

We're approaching 3000 source files in our repo so I'm not sure. That is the issue.

[ Parent | on HN ]

Re:VSCode memory leak issue marked “out-of-scope” by brundolf on Tuesday November 24, 2020 @12:43AM (#25195660)

Here's a question: are you using git, and is node_modules ignored?

I ask because I think VSCode (by default) leans on the gitignore to decide which files to index. If it's indexing node_modules for whatever reason, that could create some serious overhead.

https://www.reddit.com/r/vscode/comments/fpfnle/is_there_a_w...

[ Parent | on HN ]

Re:VSCode memory leak issue marked “out-of-scope” by ogre_codes on Tuesday November 24, 2020 @01:05AM (#25195767)

node_modules is in our .gitignore.

I'm not sure I was super clear above, but I'm not too worried about fixing this. Now that I have a good VIM configuration I just don't feel the urge to go back.

[ Parent | on HN ]

Re:VSCode memory leak issue marked “out-of-scope” by brundolf on Tuesday November 24, 2020 @01:16AM (#25195829)

That's fair! Cheers

[ Parent | on HN ]

Re:VSCode memory leak issue marked “out-of-scope” by ogre_codes on Tuesday November 24, 2020 @01:32AM (#25195900)

Also, thanks for being rad! I do appreciate the suggestions!

[ Parent | on HN ]