Fix activity leak in Dialer

Make sure to close the contact lookup thread when ListsFragment is
destroyed, just like in CallLogFragment.

The thread was holding a reference to the outer adapter because it was
a non-static inner class, which was causing the adapter and activity to
leak.

Bug: 17472228
Change-Id: Ic2d6fbded0c8c40cf99d779fe24a535d75bc802a

1 files changed, 6 insertions, 0 deletions

diff --git a/src/com/android/dialer/list/ListsFragment.java b/src/com/android/dialer/list/ListsFragment.java
index 39efa5191..7cc519fe1 100644
--- a/src/com/android/dialer/list/ListsFragment.java
+++ b/src/com/android/dialer/list/ListsFragment.java
@@ -226,6 +226,12 @@ public class ListsFragment extends AnalyticsFragment implements CallLogQueryHand
     }
 
     @Override
+    public void onDestroy() {
+        mCallLogAdapter.stopRequestProcessing();
+        super.onDestroy();
+    }
+
+    @Override
     public View onCreateView(LayoutInflater inflater, ViewGroup container,
             Bundle savedInstanceState) {
         final View parentView = inflater.inflate(R.layout.lists_fragment, container, false);