Skip to content

fix: clear setInterval in LoadingComponent on destroy#387

Closed
wowitsjack wants to merge 1 commit intoFredolx:mainfrom
wowitsjack:fix/loading-interval-leak
Closed

fix: clear setInterval in LoadingComponent on destroy#387
wowitsjack wants to merge 1 commit intoFredolx:mainfrom
wowitsjack:fix/loading-interval-leak

Conversation

@wowitsjack
Copy link

@wowitsjack wowitsjack commented Mar 7, 2026

Full source available at FredTV-Next, my personal fork with all features integrated.

Summary

  • The LoadingComponent's setInterval was never cleared, leaking intervals on every create/destroy cycle
  • Store the interval ID and clear it in ngOnDestroy
  • Implements OnDestroy interface

Test plan

  • Open app, navigate to trigger loading component, navigate away, verify no console errors or leaked timers

@CLAassistant
Copy link

CLAassistant commented Mar 7, 2026

CLA assistant check
All committers have signed the CLA.

The loading component's setInterval was never cleared, causing leaked
intervals on every create/destroy cycle. Store the interval ID and
clear it in ngOnDestroy.
@wowitsjack wowitsjack force-pushed the fix/loading-interval-leak branch from bce1b43 to 90cf3ca Compare March 7, 2026 00:38
@wowitsjack
Copy link
Author

wowitsjack commented Mar 7, 2026

Yep, agreed

@wowitsjack wowitsjack force-pushed the fix/loading-interval-leak branch 2 times, most recently from 1e4a7d6 to 90cf3ca Compare March 7, 2026 15:54
@wowitsjack
Copy link
Author

Superseded by #396 + #397 which contribute the full FredTV-Next codebase as a proper 2-part stack.

@wowitsjack wowitsjack closed this Mar 7, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants