mdTabs: always recompiling template on tab switch (scope/watchers leak)

[andreialecu]

I'm seeing a huge scope leak when switching through tabs with watchers on them.

I was able to track it down to this:

material/src/components/tabs/js/templateDirective.js

Line 35 in f5959cc

if (ctrl.scope.noDisconnect) return;

Always being called on switching the tab, and the whole directive re-running from the beginning. The disconnect() function is never called. This seems to create a new scope and compile the template every single time.

I suspect it is related to the performance related change that was made recently, where tab content is ng-if'd out when not active, but I'm not sure.

Related: #3508

The repro there can also be used to reproduce this problem.

[andreialecu]

I found a fix for this, at:

material/src/components/tabs/js/templateDirective.js

Line 28 in f5959cc

scope.$on('$destroy', reconnect);

Needs to be changed to:

      scope.$on('$destroy', function(){
        compileScope.$destroy();
      });

Can someone familiar (@robertmesserle) with that code explain why the $destroy watcher would reconnect the scope?

I see no unintended sideffects with the above code in my scenario, but I'm unsure what the intention was there.

[piyushchauhan2011]

👍

[ThomasBurleson]

@anderson-arlen - Have you tried to using the mdNoDisconnect Tabs attribute:

<md-tabs md-no-disconnect>
  ...
</md-tabs>

And does this problem still exist with the latest code from master ?

Please provide a CodePen or Plunkr that demonstrates this issue. Here are some starter demo templates that you can use/fork:

• CodePen template: http://codepen.io/team/AngularMaterial/pen/BNYppz
• Plunkr template: http://plnkr.co/edit/yP0gB9iTacIQb48thud8?p=preview.

May be related to #3617 and #3508