I've encountered an issue where I've had to disable Typermock due to it seeming to consume (nearly) all of my system memory shortly after opening my Visual Studio solution. The issue becomes particularly acute if I attempt to build. (I have Typemock running after build disabled). Very regularly I've found VS consuming in excess of 10GB of RAM, while my co-workers will be sitting around 2GB at most.
I feel like I was encountering this intermittently before the lastest changes I started working on, but I have been working on a .NET 6 upgrade recently that (shouldn't) may be contributing?
Are there any known issues right now? Is there a compatibility issue with .NET 6? Could something be wrong in VS?
Typemock v. 9.1.5.0
VS Professional v. 17.3.5
