You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The only modification made to md-progress-circle component was to add logging when OnDestroy is called. Obviously it should log destroyed twice, but it happens only once and the interdeterminateInterval keeps running in the background causing memory leak and more cpu usage.
Note that <md-progress-circle mode="indeterminate">works and its OnDestroy method gets called, so as a workaround it's there. Also, md-spinner itself seems to work as well when not precompiled. I haven't really investigated further so I'm not sure whether it's ngc or rollup causing the issue.
The text was updated successfully, but these errors were encountered:
Fixes the `md-spinner` animation interval not being cleaned up when the app has been compiled through the AoT.
This is due to the the fact that the `ngOnDestroy` handler is in the base `MdProgressCircle` class.
Fixesangular#1283.
When using
md-spinner
withngc
androllup
itsOnDestroy
method won't run.Simple plunker example.
The only modification made to
md-progress-circle
component was to add logging whenOnDestroy
is called. Obviously it should logdestroyed
twice, but it happens only once and theinterdeterminateInterval
keeps running in the background causing memory leak and more cpu usage.Note that
<md-progress-circle mode="indeterminate">
works and itsOnDestroy
method gets called, so as a workaround it's there. Also,md-spinner
itself seems to work as well when not precompiled. I haven't really investigated further so I'm not sure whether it's ngc or rollup causing the issue.The text was updated successfully, but these errors were encountered: