J
James
I realize the Garbage Collector does a lot of this for me, but I'm having
trouble wrapping my head around something. We've been running into
System.OutOfMemoryException on our production servers running ASP.NET
1.1.4322. It's very intermittent and I don't know exactly what's causing
it. We do use a lot of a Session variables in our application and I'm
wondering if it's possible that when our load is the heaviest, if we're
storing large datasets in Session memory, that could be the cause.
From what I can gather, I don't have the ability to dispose of memory
allocated for Session variables explicitly. So assuming that our
application requires this design, how do I avoid this problem, assuming it
IS the problem in the first place?
trouble wrapping my head around something. We've been running into
System.OutOfMemoryException on our production servers running ASP.NET
1.1.4322. It's very intermittent and I don't know exactly what's causing
it. We do use a lot of a Session variables in our application and I'm
wondering if it's possible that when our load is the heaviest, if we're
storing large datasets in Session memory, that could be the cause.
From what I can gather, I don't have the ability to dispose of memory
allocated for Session variables explicitly. So assuming that our
application requires this design, how do I avoid this problem, assuming it
IS the problem in the first place?