destroy event not fired when component removed from viewport

[ratmat2000]

It seems that the destroy event is not being fired when components are removed from the viewport. This results in the component remaining in the viewports reference cache and likely not getting garbage collected. The component is getting removed from the DOM because the destroy method is being called on the component.

Here is the code I'm using to create the component. I was expecting that each time the component was destroyed (or had not been created), that the getLoginView() method would return null.

	showLoginView: function() {		
		var view;		
		if  (!(view = this.getLoginView())) {
			view = Ext.create('HealthVille.view.LoginView');
			this.getViewport().add(view);
			console.log('Created ' + Ext.getDisplayName(view));
		}
		else {
			view.show();
		}
	},

Here is the code to destroy the loginView component:

	destroyLoginView: function() {
		var view;
		if (view = this.getLoginView()) {
			var viewport = this.getViewport();
			viewport.remove(view);
	},

I have verified that the destroy method of the loginView component is being called but the reference cache in the viewport still contains a reference to the loginView.

Here is the code that is supposed to remove the component from the reference cache but the destroy event is never fired. me.refCache[ref] = null is never called.

getRef: function(ref, info, config) {
this.refCache = this.refCache || {};
info = info || {};
config = config || {};


Ext.apply(info, config);


if (info.forceCreate) {
return Ext.ComponentManager.create(info, 'component');
}


var me = this,
cached = me.refCache[ref];


if (!cached) {
me.refCache[ref] = cached = Ext.ComponentQuery.query(info.selector)[0];
if (!cached && info.autoCreate) {
me.refCache[ref] = cached = Ext.ComponentManager.create(info, 'component');
}
if (cached) {
cached.on('destroy', function() {
me.refCache[ref] = null;
});
}
}


return cached;
},

[Jamie Avins]

Thank you for the report.

[ratmat2000]

I figured out the problem here. I had custom destroy methods on my view that were not calling this.callParent(). Adding those calls back into my destroy methods fixed the problem.

[Jamie Avins]

Thank you for the clarification.