Memory leak in GuidanceStepSupportFragment [164841457]

Fixed

Bug

Status Update

No update yet.

Description

th...@gmail.com

created issue #1

Aug 17, 2020 04:46PM

Component used:androidx.leanback:leanback
Version used: 1.1.0-alpha04
Devices/Android versions reproduced on: Android 9

There is a memory leak in GuidanceStepSupportFragment. In the onDestroyView function, mGuidanceStylist.onDestroyView() is called. When looking at the implementation for that function, you can see that views are set to null. However, the field called mGuidanceContainer is not set to null here. That causes a memory leak.

Comments

th...@gmail.com <th...@gmail.com> #2Sep 20, 2020 12:56PM

Running into a similar issue, any update on this?

da...@google.com <da...@google.com> #3Sep 23, 2020 11:39PM

This is a platform behavior change.

b/236862874 is related.

ap...@google.com <ap...@google.com> #4Sep 24, 2020 03:03AM

Reassigning to current owner per go/androidx/owners.

th...@gmail.com <th...@gmail.com> #5Sep 24, 2020 10:40AM

Re-triaging by request.

da...@google.com <da...@google.com> #6Sep 24, 2020 05:06PM

Any progress?

th...@gmail.com <th...@gmail.com> #7Nov 3, 2020 05:51PM

deleted

da...@google.com <da...@google.com> #8Nov 19, 2020 11:03PM

Marked as fixed.

Thanks for the comment#1 report. The bug in how those older versions of the framework dispatch insets does make handling insets difficult. It's on our roadmap for early 2025 to prepare an AndroidX-side workaround.