Real asp.net memory leak or is visual studio to blame [closed]

As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance. Closed 11 years ago.

I've been working on a small aspx website all week; this morning I noticed that my local instance was running extremely slowly. When checked in task manager, my webdev.WebServer40.exe process had a ~1.2GB working set. After restarting visual studio and running the site for about an hour afterwards the memory total is only about 100MB.

Is this an indication that serverside code is leaking memory somewhere, or is the webserver process just inefficient about cleaning up junk that accumulates over dozens o开发者_JAVA技巧f rebuilds?

---

Most likely it's something in your code. The webserver itself isn't likely a problem, as .NET developers all over the world would have noticed it and raised a stink by now.

There's really not enough information here for us to tell you what the exact problem is. You'll need to look into it yourself or get someone who's more familiar with ASP.NET to help you. However, general guidelines are available online.

See this article for guidance for .NET in general: http://msdn.microsoft.com/en-us/library/ff647813.aspx

or

Quick things to check when you experience high memory levels in ASP.NET

or (darn, this makes the quesiton a duplicate.) here: ASP.NET Website Memory Usage quite high