Memory Leak and Objects delete

@davidckMay 04.2006

I’m fairly experienced in JavaScript and been trying to do alot of new things with it in AJAX and such.

As my app got larger, JS part took 1000+ lines, it seems I have problem managing Objects. And the performance is starting to become sluggish after 10 minutes of constantly browsing through one page, since my AJAX app do not refresh the page a single time so there’s somekind of accumulation going on… I try to be careful but the inevitable happened ?

Is there a fast way to detect ALL of the Objects I’ve created?

Thanks!

to post a comment

JavaScript

@A1ien51May 04.2006 — #I highly recommend you read this...

http://msdn.microsoft.com/library/default.asp?url=/library/en-us/ietechcol/dnwebgen/ie_leak_patterns.asp

Eric

@davidckauthorMay 04.2006 — #That's a great read. Thanks!

I found a way to loop through my objects using for (x in Object) in case anyone is interested. I will continue building my app as it is. Then use the suggested method of applying a 'null' to any unused objects.

The "leak" also happens in Firefox btw, so it's not just an IE thing. I use tools like "web developer" for firefox for zero error coding so I know I haven't made any coding error plus I use TRY CATCH on the entire prog. So it is leaking.

If there are any more ways to optimize this issue, let me know please ?

@A1ien51May 04.2006 — #Also look into: http://outofhanwell.com/ieleak/index.php?title=Main_Page

Eric

@davidckauthorMay 05.2006 — #Thx, I saw that app before. I ran it for 10 min and it couldn't detect a single leak. Now I'm wondering if the problem lies somewhere else...

@davidckauthorMay 05.2006 — #Drip is still useful, I can see how much memory is used after each request.

What I found out, it problably wasn't a leak afterall, but just an accumulation I thought the browser would take care of.

For those interested, besides the thousand lines of code, I use a package on the web (script.aculo.us) that allows some fancy effects in your AJAX application. When you do a SLIDEUP for example, your div will animate and disappear off your sight. However, the innerHTML attribute still lives thus whatever data you loaded in there is still in memory. And I kept loading data in constantly thus explaining the growing demand of ressource. Now I'm just starting to empty them up and I see significant improvement. Right now, my app loads in quite a bit of data. Although currently not an issue, I just foresee way later on when there will 10 times more data.

Thanks for suggesting Drip.

Memory Leak and Objects delete

5 Comments(s) _↴

Also in #JavaScript _↴

Success!

Social

Version

Memory Leak and Objects delete

5 Comments(s) ↴

Also in #JavaScript ↴

Success!

The web is an endless sea of information. Don't miss the boat... Subscribe!

Social

Version

5 Comments(s) _↴

Also in #JavaScript _↴