From 286d36b03b2a6a740ed9a93d83ad36c7f649f6c9 Mon Sep 17 00:00:00 2001
From: Douglas Machado <douglas.machado@valor-software.com>
Date: Wed, 27 Jul 2022 15:15:51 -0300
Subject: [PATCH] fix(android): FragmentCallbacksImplementation memory leak
 (#9977)

---
 packages/core/ui/frame/index.android.ts | 9 +++++++--
 1 file changed, 7 insertions(+), 2 deletions(-)

diff --git a/packages/core/ui/frame/index.android.ts b/packages/core/ui/frame/index.android.ts
index 056fa2fae..627541855 100644
--- a/packages/core/ui/frame/index.android.ts
+++ b/packages/core/ui/frame/index.android.ts
@@ -1031,9 +1031,14 @@ class FragmentCallbacksImplementation implements AndroidFragmentCallbacks {
 		// animation should start between start and resume, so if we have an executing navigation here it probably means the animation was skipped
 		// so we manually set the entry
 		// also, to be compatible with fragments 1.2.x we need this setTimeout as animations haven't run on onResume yet
+		const weakRef = new WeakRef(this);
 		setTimeout(() => {
-			if (frame._executingContext && !(<any>this.entry).isAnimationRunning) {
-				frame.setCurrent(this.entry, frame._executingContext.navigationType);
+			const owner = weakRef.get();
+			if (!owner) {
+				return;
+			}
+			if (frame._executingContext && !(<any>owner.entry).isAnimationRunning) {
+				frame.setCurrent(owner.entry, frame._executingContext.navigationType);
 			}
 		}, 0);