Ext Garbage Collector

[Animal]

The Garbage Collector finds orphaned Elements, that is Ext.Elements who's "dom" HtmlElements have been removed from a document.

I'm thinking it should also find Ext.Components who's elements have been removed from the document.

In my case, I'm creating an Ext.form.BasicForm when loading a fragment into a ContentPanel.

When that ContentPanel is reloaded, a new Ext.form.BasicForm is created. The old one stays registered.

I think I'm building up quite a few orphaned components in my pages.

[jack.slocum]

Yes, that was part of the plan - step by step though. ;) There are a few issues to iron out with Component garbage collection but at this point it looks promising.

[Animal]

Yep, It's the kind of thing I knew you'd have a plan for. Just checking! :)

[FuryVII]

I assume this is part of Ext 2.0 (along with the whole new component model)?

[brian.moeskau]

Actually it's in 1.1 in Element.js. It's currently just a private static function (Element.garbageCollect) that automatically runs on a 30 second interval.

[FuryVII]

Cool, thanks.

[cluettr]

Is there anyway to force the garbage collection to happen immediatly after removing an element?

[evant]

Should just be able to call:



Ext.Element.garbageCollect();

[cluettr]

Thanks Evant. Would this work asyncronously? In other words if I was to garbage collect and then during the collection recreate a div could the new div be created before the garbage collection is complete? Not sure if that is something you may be able to answer.

[evant]

Looked at the source, garbageCollect runs synchronously.

The calls are made by Ext on a timer:



El.collectorThreadId = setInterval(El.garbageCollect, 30000);

[pluesch0r]

Right now, I'm running into the same problem as animal - I've got a grid that I'm creating via Ajax; by executing the Ajax code twice, the old grid gets overwritten with the new grid .. but all the helper elements stay in the DOM.

Cheers,
Martin

[cluettr]

Does the garbagecollection function only clean up Ext elements or does it do everythign in the dom?

[GalaxySong]

Will it somehow save us from Memory Leak?

[xsbr]

Will it somehow save us from Memory Leak?

On IE isn't possible avoid memory leak... There are four days that I'm trying to destroy memory leak no IE, but I couldn't...

Is possible reduce it... look at my thread:
http://extjs.com/forum/showthread.php?t=11810

[krause]

Hi, I see this thread is quite old but it was the best existing thread I found.
Any updates for Ext 3.x?
What are the guidelines for correctly disposing of Components in order to allow for garbage collection and to prevent memory leaks?
Somebody recently asked me about this because they have quite a big Ext application all served through a single HML page and over time it consumes the memory. This is on Firefox (without firebug enabled).
I don't have a specific case, but rather I was looking for some guidelines regarding how to correctly dispose of components in the lines of "make sure you unregister all listeners that subscribed to events fire by the component you want to dispose" or "make sure you remove all records from the store"...(of course I'm making this up and is probably not correct).
I also see there are new (for Ext 3) autoDestroy config attributes for such things as stores and components, but haven't used them.

Any information will be greatly appreciated.

[dan_b]

rather I was looking for some guidelines regarding how to correctly dispose of components in the lines of "make sure you unregister all listeners that subscribed to events fire by the component you want to dispose" or "make sure you remove all records from the store"...(of course I'm making this up and is probably not correct)..

Me too.. just about to push my first "one-big-page" ExtJS app into production...

[Jamie Avins]

The garbage collector had some love back in the 3.1.x+ timeframe and does a better job at cleaning up various dom nodes that get orphaned as well as flushing out the central hash used to track events, pseudo expandos (Element.data), etc. Cleaning up you stores if they are no longer used is always important. Unregistering listeners is always a good idea if you hook into the component lifecycle, and never leave direct dom references

[Eric24]

@Jamie: It would be really useful to see an "expansion" of your comments. Something like a quick overview with some examples of what to do and what to avoid to minimize leaks in Ext code.

[richgoldmd]

I second Eric's motion...