re: SharePoint memory leak caused by incorrect web.config settings

Stefan Goßner — Mon, 23 Jul 2012 09:19:40 GMT

Hi Ashish,

by reviewing the ULS log after enabling callstacks.

Callstacks can be enabled using the information from these articles:

SharePoint 2007:

blogs.technet.com/.../troubleshooting-spsite-spweb-leaks-in-wss-v3-and-moss-2007.aspx

SharePoint 2010:

blogs.technet.com/.../sprequest-allocation-callstack-logging-in-sharepoint-2010-and-wss-4-0.aspx

Then check if the callstack is similar to the one I listed here in the article.

btw: the easiest check is to verify that the setting in the web.config is correct. ;-)

Cheers,

Stefan

re: SharePoint memory leak caused by incorrect web.config settings

Ashish Mishra — Mon, 23 Jul 2012 06:14:24 GMT

Hi Stefan,

Nice article but how to know that the problem is because of batch compilation without going into the config file because people mostly look for other reasons such as memory leak because of object or some other coding issues.