Too much change detection
With the default strategy, Angular potentially checks the whole component tree on every event, timer or HTTP response. Missing OnPush, function calls in templates and frequent events not moved out via NgZone.runOutsideAngular multiply the effort.
RxJS subscriptions that never end
Subscriptions that aren't closed when a component is destroyed – e.g. without the async pipe, takeUntilDestroyed or toSignal – keep components, DOM nodes and data in memory. This is the most common source of memory leaks.
Other memory leaks
Manually registered event listeners, setInterval timers, third-party libraries that don't clean up, or ever-growing caches in services lead to detached DOM nodes and a steadily growing heap.
Inefficient rendering of large data sets
Lists without a track expression (or trackBy), missing virtualisation and computations in templates make Angular rebuild far too much DOM on every change.
State management without memoisation
NgRx selectors that create new objects on every call, or complex derivations without createSelector or computed(), trigger rendering even though nothing has changed.
Oversized bundles
Missing lazy loading of routes, no @defer for heavy components and unused dependencies increase load time – especially on mobile devices.