Re:Greppability is an underrated code metric
by cma on Tuesday September 03, 2024 @08:39AM
(#41434386)
If running into this, make sure to enable 64-bit intellisense and increase the ram limit, by default it is 4gb.
Re:Greppability is an underrated code metric
by Cieric on Tuesday September 03, 2024 @03:29PM
(#41438293)
As someone who runs into that daily, I'm surprised I never heard of this before.
I seem to have found the 64-bit mode under "Tools > Options" then "Text Editor > C/C++ > IntelliSense". The top option is [] Enable 64-bit IntelliSense.
But I can't seem to find the ram limit you mentioned and searching for it just keeps bringing up stuff related to vscode. Do you know where it is off the top of your head or a page that might describe it?
Re:Greppability is an underrated code metric
by samatman on Tuesday September 03, 2024 @06:51PM
(#41440120)
The RAM limit is 32 bit Intellisense. 2^32 is 4GiB.
Edit: I take that back, this was a first-principles comment. There's a setting 'C_Cpp: Intelli Sense Memory Limit' (space included).
Re:Greppability is an underrated code metric
by Cieric on Wednesday September 04, 2024 @10:22AM
(#41446189)
Thanks for that, while searching google for that result only lead me to vscode's IntelliSense settings. Searching for "Intelli Sense Memory Limit" setting in visual studio didn't lead me right to the result but it did give me a whole settings page that "matched". I found the setting in visual studio is "IntelliSense Process Memory Limit" which is under "Text Editor > C/C++ > Advanced" then under header "IntelliSense" towards the bottom of the section.
We also had a livegrep instance that we could use to grep any corporate repo, regardless of where it was hosted. That was extremely useful for investigating failures in build scripts that spanned multiple repositories (e.g. building a Go sidecar that relies on a service config in the Java monorepo).