Just finished reading Todd Carter’s journey of tracking down a Sasquatch SharePoint object model memory leak. Wow! We’ve been working on cleaning up some of our client’s code according to the best practices document concerning using disposable Windows SharePoint Services objects (I’m not sure…looks more like an excuse document to me) and I’m beginning to believe that this may be the root of our problems. There’s lots of custom code in this SharePoint application and we’re seeing application pool recycles every few minutes. The biggest problem seems to be when we attempt to download a large (> 400Mb) file from SharePoint via the custom object model code.
Richard Wixom, of DNSalePrice fame, has been working hard debugging this issue. We may just be on to something! We’ll let Todd (and others) know if this turns out to be the root cause.
Are you a user? 
0 Responses to “Tracking Down a “Sasquatch” Memory Leak”