Recent searches
Search options
Left VS2022 going for an hour, by that point it was using 6GB of RAM and was still sat on 100% of one core.
No idea what the hell that thing is playing at (and I can't find a way to tell, and even if there is the UI is so unresponsive I'm not sure I could get to it!), so time to verify the UE5.5 install and the VS2022 install I guess...
So everything verified, project refreshed, etc.
Still doing the same thing.
I suspect that it isn't a coincidence that this seems to have started after updating VS2022 to 17.12.3
Fuck's sakes...
@JeremiahFieldhaven There's a person on Mastodon that was posting about using superluminal to profile VS to figure out why it was taking so long to open projects. I can look them up for you if you want.
@obsurveyor Thanks, but it's gone over my "can be arsed with this" horizon.
I've switched to VSCode for now, and that at least isn't using multi-GB of RAM.
Half tempted to just set up emacs at this point...