ListItem doesn't destroy its header element

[artsiom_aliakseyenka]

REQUIRED INFORMATION




Ext version tested:

• Sencha Touch 2.1

Browser versions tested against:

• Chrome 23(Windows)

Description:

• Ext.List component consists of Ext.dataview.component.ListItem components.
• Every ListItem contains three elements: body, dislosure, header.
• When ListItem is created, it places body and dislosure in the items collection. But header is simply inserted in dom.
• When list is created with some data populated, then we have no any problems.
• But when list created empty, without data or store, then we have following problem:
  • List subscribed on resize event.
  • When resize is fired(it always fired, even if window size wasn't changed), the list, when it is empty, adds empty items.
  • If after that we destroy list, the header items for every list item element are not destroyed.
  • This also happens when, after creating empty, list was populated with data, and then destroyed. Those empty list items are not fully destroyed

Steps to reproduce the problem:

• Create empty List
• Let resize event to be fired, wait some time
• Destroy List and check Ext.StoreManager.map, you will find there header components, which are not destroyed, although list is destoyed

The result that was expected:

• ListItem should destroy its header

The result that occurs instead:

• ListItem's header is not destroyed

Test Case:

        var list = Ext.create('Ext.List', {
            fullscreen: true,
            itemTpl: '{title}'
        });


        setTimeout(function(){
            list.destroy();
            console.log(Ext.ComponentManager.map); // contains several ext-component, which are the listitem's header
        },1000);

[mitchellsimoens]

The reason for the header is since the list supports infinite dataset, you never know which row will need to show a header. So as you scroll a header may need to be shown on any of the list items so they need to be there.

[artsiom_aliakseyenka]

Yeap, i understand this. But this doesn't explain why headers are not destroyed. If they would be never destroyed , we will have a leak.

[artsiom_aliakseyenka]

Mitchell, i mean the following. Lists in most cases will be created empty. And the headers created for empty list items elements, which i described above, will be never destroyed. In case we have many lists, or list is repeatedly created/destroyed, the memory will grow, this causes memory leak.

[mitchellsimoens]

I see the issue with your test case, you were looking at StoreManager not ComponentManager.

[artsiom_aliakseyenka]

Oh, sorry, my mistake