Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
HomeAnnouncementsFree MagazinesWhite PapersSubmit Content
Discussion GroupsASP.NETWindows FormsLanguages.NET FrameworkVisual Studio.NET
Articles.NET FrameworkASP.NETToolsWindows Forms
.NET DirectoryOpen Source ProjectsUser GroupsWeb Resources
Related Topics
Visual Basic 6SQL ServerMS AccessOther DB ProductsMS Server ProductsMore Topics ...

.NET Forum / Languages / C# / October 2007

Tip: Looking for answers? Try searching our database.

Memory Leak IE Javascript attribute add onblur

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Joshua - 02 Oct 2007 18:06 GMT
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] - 02 Oct 2007 18:19 GMT
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.

Signature

         - Nicholas Paldino [.NET/C# MVP]
         - mvp@spam.guard.caspershouse.com

The javascript engine on the client side in IE

> I'm running into an issue with a memory leak in an Asp.Net web page.
>
[quoted text clipped - 7 lines]
>
> Thank you very much.
Ignacio Machin ( .NET/ C# MVP ) - 02 Oct 2007 18:37 GMT
Hi,

> 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?

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 - 03 Oct 2007 15:48 GMT
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.

Free Magazines

Get these publications absolutely FREE for up to 12 months. There are no hidden fees and no obligation. Simply choose a title, complete the application form and submit it. Read more ...

Oracle MagazineNetwork ComputingComputer WorldBio-IT WorldeWeekInformation WeekInfosecurity
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.