Hi, We have a app in production where we are seeing a bunch of these errors & we believe its being caused by an internal Collection of objects that we maintain (for each request) throughout the life of the request We strongly suspect that at times this collection is not getting cleaned up properly & thus causing memory leaks. The correct solution would to see that the collection is null'd for the requests at all exit points. I am afraid we dont have the time to identify all these as quickly as we need the solution. Are there any suggestions that folks over here can make on how to track the culprit requests still hanging in memory... Of course, we don't want to eradicate the ones that are still in process... only the ones that are done processing. thx
We haven't really pointed out the exact place using a profiler in the dev env... but we found from a production monitoring tool that this collection is the culprit. So, we did use a tool - now we need to find a way to fix this hole... or at least clean up after it.