> I'm running into an issue with a memory leak in an Asp.Net web page.
>
[quoted text clipped - 5 lines]
>
> Does anybody know how to kill these when I exit the page?
On Oct 2, 10:37 am, "Ignacio Machin \( .NET/ C# MVP \)" <machin TA
laceupsolutions.com> wrote:
> Hi,
>
[quoted text clipped - 12 lines]
>
> Are you sure that is the problem?
I'm using Drip to identify these because the javascript garbage
collector is not taking care of it. After using the page for a while,
entering and exiting, the memory grows so much that they have to close
the browser and reopen it - it grows and does not go down after
exiting the page or even the site. I'm tacking the memory using the
task manager, process tab watching iexplore.exe. I'm using IE 7 (or
6). However the Drip program I saw was suggested by others to
identify open DOM calls (in reference to leaked memory). I'm just not
sure how to kill the open DOM calls. Is there some javascript call
that I can use on the unload to kill these?
The page has some ajax toolkit items (calendar and cascading dropdown)
and makes some web service calls as well.