View Full Version : [FIXED-456][3.1] TreeLoader should abort any existing connection on destroy

19 Jan 2010, 11:07 AM
Ext version tested:

Ext 3.1

Adapter used:


css used:

only default ext-all.css

Browser versions tested against:

Not a browser specific bug

Operating System:

Not an OS specific bug


If a tree loader is currently loading data and then destroyed while still loading the active transaction is not aborted.

Possible fix:

destroy : function(){

Jamie Avins
19 Jan 2010, 4:23 PM
Do you have a test case which demonstrates the issue?

Relying on abort isn't going to reliably fix the issue. If this is similar to the store callbacks, an additional check before the runCallback is executed is going to be necessary to make sure the component in question isn't destroyed.

Jamie Avins
1 Feb 2010, 2:22 PM
Abort was added in svn 5973. If you have an issue with the connection still returning, additional isDestroyed checks will need to be added for the callback function.