Fix ViewBinding memory leak in MediaDetailFragment

[Roniscend]

Description (required)

Fixes #6827
Set _binding = null in onDestroyView() to release the view hierarchy reference when the fragment view is destroyed

Tests performed (required)

Tested 6.4.0-debug on Pixel 9 (Android 16)

[Copilot]

Pull request overview

Fixes the reported ViewBinding leak in MediaDetailFragment by clearing the fragment’s view binding reference when the view is destroyed (Fragment view lifecycle best practice).

Changes:

• Set _binding = null in onDestroyView() to release references to the fragment’s view hierarchy.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[github-actions]

✅ Generated APK variants!

• 🤖 Download prodDebugAPK
• 🤖 Download betaDebugAPK

[neeldoshii]

LGTM!

[Roniscend]

@nicolas-raoul @RitikaPahwa4444 can you please review this pr

[chrisdebian]

Confirmed the core fix is correct — _binding = null in onDestroyView() does release the view hierarchy reference. One thing worth flagging: nulling _binding here exposes 4 pre-existing NPE risks in async callbacks that touch the view after destroy (a raw view.post, two OnGlobalLayoutListeners, and Fresco's ControllerListener) — I hit this directly on-device (fast-swiping the photo pager reliably reproduced it) while working on #6914, which includes this same line plus guards for those four call sites. Not a reason to block this PR, just worth knowing before merging standalone — happy to point to the exact guard code if useful.