Ivy is leaking memory

🐞 bug report

Affected Package

The issue is caused by package @angular/core@9.0.0-rc.14 and earlier versions as well.

Is this a regression?

Yes, the previous version in which this bug was not present was: View Engine

Description

Ivy is leaking memory by holding onto component references in some manner.

🔬 Minimal Reproduction

https://ng-run.com/edit/tvqV5P78BchpccNmW4XU?open=app%2Fapp.component.ts&aot=true

All this application does is create a dynamic component (TabComponent) and then immediately destroy it, within the AppComponent ngOnInit method.

In Chrome, take a memory heap snapshot of the ‘ng-run-preview.firebaseapp.com’ instance. Search for tabcomponent: …the destroyed component is still in memory.

On the left-hand sidebar of ng-run, click “Base Project” and then turn “Ivy AOT” off.

After the app reloads, take another heap snapshot and perform the same search. …the destroyed component is gone from memory, which is expected.

Note: This issue might be related to #35148

[Achilles1515]

@christianliebel, as I referenced your issue.

[Achilles1515]

@Achilles1515 ha! you are right. Regarding LComponentView_TabComponent - my understanding is that it should be present in the dev mode only (window.ngDevMode being truthy). A project build with AOT in production mode should not have this problem.

Cool. So I believe this issue can be closed. Yeah…ng-run is great, but finicky. I also just recently realized that the ng-run.preview.firebaseapp.com heap dumps share memory across open tabs. So I really should have said “Close all incognito windows and open the ng-run in a fresh one”.