-
Notifications
You must be signed in to change notification settings - Fork 0
Description
So I'm not sure if the updates from mid January of this year are the cause of this, but I'd noticed for about 3 or so months now that my Visual Studio's memory usage (via checking the commit used/total in Task Manager) was steadily going up, and I know it was Visual Studio because the commit would go down when restarting Visual Studio. On a whim, I disabled ResourceMonitor (as I don't have it installed on my work machine and it hasn't been having these issues), and memory has not ballooned out of control since. To me this feels like ResourceMonitor now has a memory leak somewhere, but I have no idea where it would be leaking memory or why. I only started realizing the possibility of this back in February when I started to get some out of memory errors all over the place, and only just last month noticed the commit size basically maxing out, and it was only then that I found that restarting Visual Studio would keep the commit in check.