Memory Leak is it?

Question

I have this small chunk of code and I can't understand why it's taking soo memory.

    static void Main(string[] args)
    {
        using (SPSite mySite = new SPSite("http://consotvo.internal.com/upi"))
        {
            using (SPWeb web = mySite.OpenWeb())
            {
                //foreach (SPFile file in web.Files[0])
                //    Console.WriteLine(file.Name);

                SPFile file = web.Files[0];

                using (SPLimitedWebPartManager manager = file.GetLimitedWebPartManager(PersonalizationScope.Shared))
                {
                    foreach (System.Web.UI.WebControls.WebParts.WebPart wb in manager.WebParts)
                    {
                        Console.WriteLine(wb.Title);


                        //wb.Dispose();
                        //manager.Web.Dispose();
                    }

                }
            }
        }
    }

This code is consuming 97,868 k even after code has been executed even thought i didn't closed console window yet. my problem is that i want to open 3000 webs (different url) and make changes to a webpart but too much memory is being consumed.

Answer 1

I'd guess the culprit would be:

SPFile file = web.Files[0];

This will load the entire collection into memory, even though you are only after a specific file.

Use SPWeb.GetFile() instead.

Edit

Additionally, SharePoint 2007 and WSS 3.0 Dispose Patterns by Example provides an example of using the SPLimitedWebPartManager, that requires an explicit Dispose() call on SPLimitedWebPartManager.Web:

using (SPSite siteCollection = new SPSite("http://moss"))
{
    using (SPWeb web = siteCollection.OpenWeb())
    {
        SPFile page = web.GetFile("Source_Folder_Name/Source_Page");
        using (SPLimitedWebPartManager webPartManager = page.GetLimitedWebPartManager(PersonalizationScope.Shared))
        {
            try
            {
                // ...
            }
            finally
            {
                webPartManager.Web.Dispose();
            }
        }
    } // SPWeb object web.Dispose() automatically called
}  // SPSite object siteCollection.Dispose() automatically called

Also, there is a fairly lengthy description of this issue by Bryan Napier here: SPLimitedWebPartManager Memory Leak?

Edit 2

The above SPLimitedWebPartManager.Web memory leak is apparently fixed in SP2010.