For those who use VS Code, you might need enabled the setting for re-opening a beforehand open file subsequent time the app launches. I do. I like that.
However typically you actually, actually don’t need that to occur.
I not too long ago bumped into a kind of occasions! I needed to reinstall my native copy of this web site and, with it, the 3GB+ database that accompanies it. Being a WordPress web site and all, I wanted to open up the SQL database file to search-and-replace some stuff.
For those who’ve ever tried to open a brilliant duper massive file in VS Code, then you recognize you may have to jiggle just a few settings that enhance the reminiscence restrict and all that. The app is tremendous versatile like that. There’s even a good extension that’ll each enhance the reminiscence and carry out a search-and-replace on open.
Anyway, that huge ol’ database file crashed VS Code a number of occasions and I wound up discovering one other option to go about issues. Nevertheless, VS Code retains making an attempt to open that file and inevitably crashes despite the fact that I nuked the file. And which means I anticipate the MacOS beachball of enjoyable to spin round earlier than the app crashes and I can reopen it once more for reals.
Properly, I lastly determined to repair that at present and spent a bit time looking out round. One Stack Overflow thread suggests disabling extensions and rising the reminiscence restrict through the command line. I’m glad that labored for some of us, however I needed to maintain trying.
One other thread suggests clearing the app’s cache from the command palette.
Good, however no cube. 🎲
I wound up going with a scorched earth technique shared by Jie Jenn in a useful YouTube video. You’ve gotta manually trash the cached recordsdata from VS Code. The video walks by it in Home windows, but it surely’s fairly darn related in MacOS. The VS Code cache is positioned in your consumer folder.
Discover that I’ve the Backups folder highlighted there. Jie eliminated the recordsdata from the CachedData folder, however all that did was set off a immediate for me to re-install the app. So, I took a threat and deleted what seemed to be a 3GB+ file in Backups. I confirmed that file the door and VS Code has been comfortable ever since.
Ask me once more in per week and perhaps I’ll discover out that I actually screwed one thing up. However to this point, so good!
