Closed ericwinger closed 3 years ago
I was able to determine that the spike in temp obj space usage was very sudden using vsd. I don't recall doing much except for logging out. Something perhaps in the logout went awry?
Going to close this - Believe the problem just happened to manifest around a logout but was caused by excessive instances of ClassOrganizer which has now been fixed.
I don't have a reproduction case yet, but sometimes I get this error when logging out of a gci connection. This only started recently. Recording the issue for tracking until it's reliably reproducable. Loaded sha's are: