Memory Leak IE Javascript attribute add onblur

[Joshua]

I'm running into an issue with a memory leak in an Asp.Net web page.

In the code behind (.cs) I'm adding onchange, onblur and onfocus
events to a bunch of objects that reside on my page (textboxes and
dropdownlist).

After using Drip i've found that these are leaving open DOM objects.

Does anybody know how to kill these when I exit the page?

Thank you very much.

 

[Nicholas Paldino [.NET/C# MVP]]

Joshua,

For most any browser that has a javascript engine, there is a garbage
collector which will take care of this for you.

Which browser are you working with? If you exit the page, then
eventually, the gc for the javascript engine should eventually clean things
up.

 

[Ignacio Machin \( .NET/ C# MVP \)]

Hi,

I'm running into an issue with a memory leak in an Asp.Net web page.

In the code behind (.cs) I'm adding onchange, onblur and onfocus
events to a bunch of objects that reside on my page (textboxes and
dropdownlist).

After using Drip i've found that these are leaving open DOM objects.

Does anybody know how to kill these when I exit the page?

That should not be a problem. Javascript is managed, it means that you don't
have to release the memory.

Are you sure that is the problem?

 

[Joshua]

Hi,







That should not be a problem. Javascript is managed, it means that you don't
have to release the memory.

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.