ASP.NET Memory: Thou shalt not store UI objects in cache or session scope Surprisingly the issue I wrote about in "the eventhandlers that made the memory baloon" (Jan 2006) is something that still happens very frequently, I reference it in cases at least a few times a month. Just this last week I had different variations of it crop up in different cases so in this post I will show a different variation, what to look out for and how to identify it.
Problem description:
The issue here is a quick growth in memory, eventually causing OutOfMemory exceptions.
The problem:
The problem in this case was that the application stored UI controls in session scope, i.e. Labels, DataGrids etc. in order to keep relevant information about the user throughout the session. The ...
Go to the complete details ...