fix(core): cleanup _ejsa when app is destroyed#59492
fix(core): cleanup _ejsa when app is destroyed#59492arturovt wants to merge 1 commit intoangular:mainfrom
_ejsa when app is destroyed#59492Conversation
|
Generally speaking the |
|
|
|
c8ca84b to
301d77a
Compare
_ejsa when app is destroyed
301d77a to
9c72e21
Compare
|
@arturovt Can you add tests for this so we don't regress in the future? |
There was a problem hiding this comment.
I believe the method that's used below is:
clearAppScopedEarlyEventContract(appId);
There was a problem hiding this comment.
Reused that function.
9c72e21 to
beaad8d
Compare
In this commit, we delete `_ejsa` when the app is destroyed, ensuring that no elements are still captured in the global list and are not prevented from being garbage collected.
beaad8d to
08437e5
Compare
|
This PR was merged into the repository by commit f6e9776. The changes were merged into the following branches: main, 19.1.x |
In this commit, we delete `_ejsa` when the app is destroyed, ensuring that no elements are still captured in the global list and are not prevented from being garbage collected. PR Close #59492
In this commit, we delete `_ejsa` when the app is destroyed, ensuring that no elements are still captured in the global list and are not prevented from being garbage collected. PR Close angular#59492
|
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
In this commit, we delete
_ejsawhen the app is destroyed, ensuring that no elements are still captured in the global list and are not prevented from being garbage collected.