gpt4 book ai didi

Android:LocationManager 泄漏,即使调用了removeUpdates

转载 作者:行者123 更新时间:2023-12-02 10:17:40 25 4
gpt4 key购买 nike

我已经实现了一个 fragment ,用于获取设备的 GPS 位置。由于某种原因,我遇到了内存泄漏 - 即使我注销了监听器(正如所有有关 LocationManager 内存泄漏的帖子中所建议的那样)。我对 Android 还比较陌生,所以这可能是完全愚蠢的事情。

public class GetLocationTask extends Fragment {

/**
* Callback interface through which the fragment will report the
* task's progress and results back to the Activity. Calling activity MUST implement this.
*/
public interface LocationCallbacks {
void onLocationReceived(double latitude, double longitude);
}

/** The calling activity. */
private LocationCallbacks mCallbacks;

private LocationManager locationManager;
private LocationListener locationListener;

/** Create a new instance. */
public static GetLocationTask newInstance() {
GetLocationTask f = new GetLocationTask();

// Supply index input as an argument.
Bundle args = new Bundle();
f.setArguments(args);

return f;
}

@Override
public void onAttach(Context activity) {
super.onAttach(activity);
if (activity instanceof LocationCallbacks) {
mCallbacks = (LocationCallbacks) activity;
} else {
Log.w("GetLocationTask", "CALLING CLASS DOES NOT IMPLEMENT INTERFACE!");
}
}

@Override
public void onCreate(Bundle savedInstanceState) {
super.onCreate(savedInstanceState);
setRetainInstance(true);

locationManager = (LocationManager) getActivity().getSystemService(Context.LOCATION_SERVICE);
locationListener = new LocationListener() {
@Override
public void onStatusChanged(String provider, int status, Bundle extras) {

}

@Override
public void onProviderEnabled(String provider) {

}

@Override
public void onProviderDisabled(String provider) {

}

public void onLocationChanged(Location location) {
if (location != null) {
double longitude = location.getLongitude();
double latitude = location.getLatitude();

locationManager.removeUpdates(locationListener);

mCallbacks.onLocationReceived(latitude, longitude);
Log.i("result", longitude + " >> " + latitude);
} else {
Log.i("waiting", "warming up still");
}
}
};


try {
locationManager.requestLocationUpdates(LocationManager.GPS_PROVIDER, 1000, 90, locationListener);
} catch (SecurityException e) {
Log.i("TODO", "TODO");
}

}

@Override
public void onDestroy() {
super.onDestroy();
if (locationManager != null && locationListener != null) {
locationManager.removeUpdates(locationListener);
}
locationListener = null;
locationManager = null;
}

@Override
public void onDetach() {
super.onDetach();
mCallbacks = null;
}
}

最佳答案

您可以通过不让 locationListener 引用任何与 fragment 相关的内容来防止内存泄漏。

您将 LocationListener 创建为匿名类,因此它具有对 fragment 的引用,并且还直接引用作为 fragment 属性的 mCallbacks

将 locationListener 定义为一个单独的类,您只需在 fragment 中实例化该类,然后将回调接口(interface)作为构造函数参数传递给监听器类,或者更好的是,观察 locationlistener 上的 LiveData 实例(显然使用 fragment 的生命周期所有者)。

关于Android:LocationManager 泄漏,即使调用了removeUpdates,我们在Stack Overflow上找到一个类似的问题: https://stackoverflow.com/questions/48456729/

25 4 0
Copyright 2021 - 2024 cfsdn All Rights Reserved 蜀ICP备2022000587号
广告合作:1813099741@qq.com 6ren.com