Notice that I have the Backups folder highlighted there. The VS Code cache is located in your user folder. The video walks through it in Windows, but it’s pretty darn similar in MacOS. You’ve gotta manually trash the cached files from VS Code. I wound up going with a scorched earth strategy shared by Jie Jenn in a helpful YouTube video. I’m glad that worked for some folks, but I had to keep looking.Īnother thread suggests clearing the app’s cache from the command palette. One Stack Overflow thread suggests disabling extensions and increasing the memory limit via the command line. Well, I finally decided to fix that today and spent a little time searching around.
And that means I wait for the MacOS beachball of fun to spin around before the app crashes and I can reopen it again for reals. However, VS Code keeps trying to open that file and inevitably crashes even though I nuked the file. There’s even a nice extension that’ll both increase the memory and perform a search-and-replace on open.Īnyway, that big ol’ database file crashed VS Code several times and I wound up finding another way to go about things. If you’ve ever tried to open a super duper large file in VS Code, then you know you might need to jiggle a few settings that increase the memory limit and all that.
Being a WordPress site and all, I needed to open up the SQL database file to search-and-replace some stuff. I recently ran into one of those times! I had to reinstall my local copy of this site and, with it, the 3GB+ database that accompanies it. Hey, thanks for remembering, buddy! 🤗īut sometimes you really, really don’t want that to happen. If you use VS Code, you might have enabled the setting for re-opening a previously open file next time the app launches.
0 kommentar(er)
