Potential Memory Leak With Inactive md-tab

[nkoterba]

In relation to #1982, I'm including code in my directives' controllers that prints out when controllers are destroyed.

For example:

       $scope.$on('$destroy', function () {
        $log.debug('Destroying: file-grid-ctrl');

        // Add any cleanup/tear-down logic here
    });

Based on my exploration of the code and the documentation, internal non-active tab content is removed from the $scope\$digest cycle:

https://material.angularjs.org/#/api/material.components.tabs/directive/mdTabs:

As a performance bonus, if the tab content is managed internally then the non-active (non-visible) tab
contents are temporarily disconnected from the $scope.$digest() processes; which restricts and optimizes
DOM updates to only the currently active tab.

Since Material Design detaches inactive Tab content from the $scope/$digest cycle, none of my controllers for all my "inactive" tabs print out Destorying: file-grid-ctrl. This leads me to believe that any resources or other things I may be "destroying/tearing down/disposing" of in my $destroy callback are not being called, leading to potential memory issues.

Perhaps instead when tabs are removed or destroyed, they should be "re-connected" to the $scope/$digest cycle right before destruction?

[sondreb]

Is there any workaround to this issue? I have a bunch of directives within tabs that needs the $destroy event to clean up a lot of resources. Will this behavior change?

[sondreb]

LumX behaves as expected, where loaded directives within the tabs all receive the $destroy event. Following this issue and reverting back to Angular Md tab-control whenever there is a workaround available.

[sondreb]

Was this behavior changed, so it always calls $destroy now?