如何修复 Frame Layout 中的内存泄漏问题?

5
我在我的Android应用程序中使用了LeakCanary,它检测到FrameLayout泄漏,但我无法找到或解决这个问题。
如何修复这个泄漏?请参考我的LeakCanary报告。
 ┬───
    │ GC Root: System class
    │
    ├─ leakcanary.internal.InternalLeakCanary class
    │    Leaking: NO (MainActivity↓ is not leaking and a class is never leaking)
    │    ↓ static InternalLeakCanary.resumedActivity
    ├─ com.android.zigmaster.MainActivity instance
    │    Leaking: NO (MapViewFragment↓ is not leaking and Activity#mDestroyed
    │    is false)
    │    mApplication instance of com.android.zigmaster.MyApplication
    │    mBase instance of androidx.appcompat.view.ContextThemeWrapper
    │    ↓ ComponentActivity.mActivityResultRegistry
    ├─ androidx.activity.ComponentActivity$2 instance
    │    Leaking: NO (MapViewFragment↓ is not leaking)
    │    Anonymous subclass of androidx.activity.result.ActivityResultRegistrythis$0 instance of com.android.zigmaster.MainActivity with mDestroyed =
    │    false
    │    ↓ ActivityResultRegistry.mKeyToCallback
    ├─ java.util.HashMap instance
    │    Leaking: NO (MapViewFragment↓ is not leaking)
    │    ↓ HashMap.table
    ├─ java.util.HashMap$HashMapEntry[] array
    │    Leaking: NO (MapViewFragment↓ is not leaking)
    │    ↓ HashMap$HashMapEntry[].[4]
    ├─ java.util.HashMap$HashMapEntry instance
    │    Leaking: NO (MapViewFragment↓ is not leaking)
    │    ↓ HashMap$HashMapEntry.value
    ├─ androidx.activity.result.ActivityResultRegistry$CallbackAndContract instance
    │    Leaking: NO (MapViewFragment↓ is not leaking)
    │    ↓ ActivityResultRegistry$CallbackAndContract.mCallback
    ├─ androidx.fragment.app.FragmentManager$10 instance
    │    Leaking: NO (MapViewFragment↓ is not leaking)
    │    Anonymous class implementing androidx.activity.result.
    │    ActivityResultCallback
    │    ↓ FragmentManager$10.this$0
    ├─ androidx.fragment.app.FragmentManagerImpl instance
    │    Leaking: NO (MapViewFragment↓ is not leaking)
    │    ↓ FragmentManager.mParent
    ├─ com.android.zigmaster.ui.trips.FragmentTripPlanner instance
    │    Leaking: NO (Fragment#mFragmentManager is not null)
    │    ↓ FragmentTripPlanner.mMap
    │                          ~~~~
    ├─ com.google.android.gms.maps.GoogleMap instance
    │    Leaking: UNKNOWN
    │    Retaining 765.4 kB in 10828 objects
    │    ↓ GoogleMap.zzg
    │                ~~~
    ├─ com.google.android.gms.maps.internal.zzg instance
    │    Leaking: UNKNOWN
    │    Retaining 142 B in 2 objects
    │    ↓ zza.zza
    │          ~~~
    ├─ com.google.maps.api.android.lib6.impl.bn instance
    │    Leaking: UNKNOWN
    │    Retaining 765.0 kB in 10821 objects
    │    A instance of com.android.zigmaster.MyApplication
    │    ↓ bn.w
    │         ~
    ├─ android.widget.FrameLayout instance
    │    Leaking: UNKNOWN
    │    Retaining 2.9 kB in 65 objects
    │    View not part of a window view hierarchy
    │    View.mAttachInfo is null (view detached)
    │    View.mWindowAttachCount = 1
    │    mContext instance of com.android.zigmaster.MyApplication
    │    ↓ View.mParent
    │           ~~~~~~~
    ╰→ android.widget.FrameLayout instance
    ​     Leaking: YES (ObjectWatcher was watching this because com.google.android.
    ​     gms.maps.SupportMapFragment received Fragment#onDestroyView() callback
    ​     (references to its views should be cleared to prevent leaks))
    ​     Retaining 1.9 kB in 48 objects
    ​     key = 265fafb3-b2a3-4462-a4e7-d5cc2afbc6fe
    ​     watchDurationMillis = 57439
    ​     retainedDurationMillis = 52422
    ​     View not part of a window view hierarchy
    ​     View.mAttachInfo is null (view detached)
    ​     View.mWindowAttachCount = 1
    ​     mContext instance of com.android.zigmaster.MainActivity with
    ​     mDestroyed = false
    
   

以下是我的XML代码:

XML:
<?xml version="1.0" encoding="utf-8"?>
<androidx.coordinatorlayout.widget.CoordinatorLayout xmlns:android="http://schemas.android.com/apk/res/android"
    xmlns:tools="http://schemas.android.com/tools"
    android:layout_width="match_parent"
    android:layout_height="match_parent"
    tools:context=".ui.trips.FragmentTripPlanner">


    <androidx.fragment.app.FragmentContainerView
        android:id="@+id/map"
        android:name="com.google.android.gms.maps.SupportMapFragment"
        android:layout_width="match_parent"
        android:layout_height="match_parent" />

</androidx.coordinatorlayout.widget.CoordinatorLayout>

这是我的片段 片段:

import android.os.Bundle
import android.view.LayoutInflater
import android.view.View
import android.view.ViewGroup
import androidx.fragment.app.Fragment
import com.google.android.gms.maps.CameraUpdate
import com.google.android.gms.maps.CameraUpdateFactory
import com.google.android.gms.maps.GoogleMap
import com.google.android.gms.maps.SupportMapFragment
import com.google.android.gms.maps.model.LatLng



class MapViewFragment : Fragment() {

    private lateinit var mMap: GoogleMap
    private var userLatitude     = 38.2500486
    private var userLongitude    = -85.7647484
    private lateinit var mapFragment : SupportMapFragment

    private var binding : MapViewFragmentBinding ?=null

    private fun zoomingLocation(): CameraUpdate {
        return CameraUpdateFactory.newLatLngZoom(LatLng(userLatitude, userLongitude), 14f)
    }

    private fun configActivityMaps(googleMap: GoogleMap): GoogleMap {
        // set map type
        googleMap.mapType = GoogleMap.MAP_TYPE_NORMAL
        // Enable / Disable zooming controls
        googleMap.uiSettings.isZoomControlsEnabled = false

        // Enable / Disable Compass icon
        googleMap.uiSettings.isCompassEnabled = true
        // Enable / Disable Rotate gesture
        googleMap.uiSettings.isRotateGesturesEnabled = true
        // Enable / Disable zooming functionality
        googleMap.uiSettings.isZoomGesturesEnabled = true

        googleMap.uiSettings.isScrollGesturesEnabled = true
        googleMap.uiSettings.isMapToolbarEnabled = true

        return googleMap
    }

    
    override fun onCreateView(
            inflater: LayoutInflater,
            container: ViewGroup?,
            savedInstanceState: Bundle?
    ): View {
        binding = MapViewFragmentBinding.inflate(inflater)

        mapFragment = (childFragmentManager.findFragmentById(R.map.id) as SupportMapFragment?)!!
        mapFragment.getMapAsync { googleMap ->
            mMap = configActivityMaps(googleMap)
            mMap.moveCamera(zoomingLocation())
        }

        return binding!!.root
    }

    override fun onDestroyView() {
        super.onDestroyView()
        
        mapFragment =null
        binding=null
    }
}
  • Build.VERSION.SDK_INT: 25

  • Build.MANUFACTURER: 三星

  • LeakCanary版本号:2.7

  • 统计信息:LruCache[maxSize=3000,hits=5750,misses=80700,hitRate=6%] RandomAccess[bytes=4089892,reads=80700,travel=60892211355,range=18101017,size=22 288421]

  • Heap dump原因:用户请求

  • 分析持续时间:29922毫秒

尝试过:同样的问题

import androidx.fragment.app.Fragment
import android.os.Bundle
import android.view.LayoutInflater
import android.view.View
import android.view.ViewGroup
import com.google.android.gms.maps.CameraUpdateFactory
import com.google.android.gms.maps.OnMapReadyCallback
import com.google.android.gms.maps.SupportMapFragment
import com.google.android.gms.maps.model.LatLng
import com.google.android.gms.maps.model.MarkerOptions

class MapsFragment : Fragment() {

    private val callback = OnMapReadyCallback { googleMap ->
        val sydney = LatLng(-34.0, 151.0)
        googleMap.addMarker(MarkerOptions().position(sydney).title("Marker in Sydney"))
        googleMap.moveCamera(CameraUpdateFactory.newLatLng(sydney))
    }

    override fun onCreateView(inflater: LayoutInflater,
                              container: ViewGroup?,
                              savedInstanceState: Bundle?): View? {
        return inflater.inflate(R.layout.fragment_maps, container, false)
    }

    override fun onViewCreated(view: View, savedInstanceState: Bundle?) {
        super.onViewCreated(view, savedInstanceState)
        val mapFragment = childFragmentManager.findFragmentById(R.id.map) as SupportMapFragment?
        mapFragment?.getMapAsync(callback)
    }
}

<?xml version="1.0" encoding="utf-8"?>
<fragment xmlns:android="http://schemas.android.com/apk/res/android"
    xmlns:tools="http://schemas.android.com/tools"
    android:id="@+id/map"
    android:name="com.google.android.gms.maps.SupportMapFragment"
    android:layout_width="match_parent"
    android:layout_height="match_parent"
    tools:context=".ui.pref.MapsFragment" />

onDestroyView 方法中,尝试将 mapFragment 设为 null 以使该字段可为空,并使用 WeakReference 作为 mMap 字段的类型。 - Santanu Sur
mapFragment = null(不起作用),请告诉我如何使用“WeakReference”。 - user15460872
那会是:WeakReference<GoogleMap>,但我认为可空性不是问题。 - Martin Zeitler
mapsFragment.onDestroy() - 当我旋转屏幕时,仍然会泄漏复制。 - user15460872
1
同样的问题,看起来谷歌已经确认这是个bug。这个问题已经被八名开发人员关注,所以你可以在该问题下发表评论,询问是否有人(包括谷歌在内)在等待修复之前有解决方法。 - Cheticamp
显示剩余3条评论
3个回答

1
起初,移除@SuppressLint("RestrictedApi")并修复您隐藏的内容。
然后尝试使private lateinit var mMap: GoogleMap成为一个本地变量...保持不需要,因为一个实例将会得到OnMapReadyCallback
也许尝试最后调用super.onDestroyView(),因为那个FrameLayout既不是层次结构的一部分,也没有被附加...而且附加计数为1,所以它必须先前已经被附加。很有可能你试图处理已经被super.onDestroyView()处理过的东西,而整个重写可能是无意义的。
猜测人们必须看看这个android.widget.FrameLayout是什么(较新的API具有布局检查器-尽管在API 25上,仍然可以将渲染的布局转储到文件)。

尝试使用局部变量、移除限制注释以及移除 onDestroyView,但仍然存在内存泄漏。 - user15460872

0

有些情况下内存泄漏是不可避免的 - 比如在使用GoogleMaps时 - 你总会从GoogleMaps片段中发现内存泄漏 - 这就是它的工作原理。虽然比2013年之前好多了,当时Google Maps 泄露 整个地图缓存,那真是太糟糕了。

无论如何,这是一个已知问题,但仍未得到解决。如果泄漏发生在由Google提供的库中,我建议不要费心。通常,它们都是已知的,如果它们很严重 - 就会被修复,如果它们很轻微 - 就会被快乐地遗忘。


0

尝试使用MapView而不是MapFragment/SupportMapFragment。 MapView扩展了FrameLayout,并针对在设备屏幕上显示地图以及其他控件的情况进行了定位,并设计用于现代平台,可以以其他方式实现。

此外,如果您只需要向用户显示地图,则可以尝试LiteModeStatic Maps API


网页内容由stack overflow 提供, 点击上面的
可以查看英文原文,
原文链接