I have one basic question:
In an ASP.NET web app, if memory is handled correctly, then after loading a page, if you then take a snapshot, then that page (even though currently displayed in the browser), shouldn't still be in memory, correct? Each request, loads/unloads the page, and renders the output. I'm seeing pages sticking around in memory and I just wanted to make sure that that's incorrect.
However, we don't have much experience in ASP.NET, and it's possible that caching can cause pages to stay in memory. Have you investigated the root paths of the pages that are not garbage collected?
SciTech Software AB
Users browsing this forum: No registered users and 1 guest