Apr 11, 2019 Admin #1 Saint_WardDon't be a Jerk.Staff memberAdministratorGold VIP ContributorJoinedMar 1, 2007Messages52,181Reaction score48,421Location Phoenix, AZOfflineAny ideas how to figure out what process is making com surrogate darn near overload my C drive (which is a SSD). I did a fair bit of googling and tried a few things, but nothing seemed to be the culprit. I'm working on checking all of my drivers now.
Any ideas how to figure out what process is making com surrogate darn near overload my C drive (which is a SSD). I did a fair bit of googling and tried a few things, but nothing seemed to be the culprit. I'm working on checking all of my drivers now.
Apr 20, 2019 Admin #2 OP OP Saint_WardDon't be a Jerk.Staff memberAdministratorGold VIP ContributorJoinedMar 1, 2007Messages52,181Reaction score48,421Location Phoenix, AZOfflineThink I solved it.
Apr 20, 2019 #3 zeetescarouserVIP Subscribing MemberJoinedJan 2, 2010Messages21,145Reaction score22,606Location the hårgaOfflinesomething was piss poorly coded using the com surrogate process (most likely older .net or vb) with a big ol’ memory leak.
something was piss poorly coded using the com surrogate process (most likely older .net or vb) with a big ol’ memory leak.
Apr 21, 2019 Admin #4 OP OP Saint_WardDon't be a Jerk.Staff memberAdministratorGold VIP ContributorJoinedMar 1, 2007Messages52,181Reaction score48,421Location Phoenix, AZOfflineI think I was just low on c drive space and the last windows update couldn't quite finish.