百度地图api android sdk leaked ServiceConnection com.baidu.location.LocationClient错误

最新推荐文章于 2019-08-01 17:49:29 发布

zhenye1986

最新推荐文章于 2019-08-01 17:49:29 发布

阅读量6.5k

点赞数

CC 4.0 BY-SA版权

分类专栏： android

本文链接：https://blog.youkuaiyun.com/zhenye1986/article/details/12781683

android 专栏收录该内容

13 篇文章

订阅专栏

本文记录了解决使用百度地图API的Android SDK时遇到的服务连接泄漏问题的过程。通过正确处理生命周期方法及在AndroidManifest.xml中配置服务节点，最终解决了泄漏问题。

摘要生成于 C知道，由 DeepSeek-R1 满血版支持，前往体验 >

最近在百度地图api 的android sdk ，下载了官方的例子运行，一切正常，然后参照定位图层写了个程序一运行，出现了以下错误：

03-29 15:36:52.300: E/ActivityThread(6484): Activity com.gif.activity.RestaurantActivity has leaked ServiceConnection com.baidu.location.LocationClient$1@40554e10 that was originally bound here03-29 15:36:52.300: E/ActivityThread(6484): android.app.ServiceConnectionLeaked: Activity com.yxtxxf.activity.RestaurantActivity has leaked ServiceConnection com.baidu.location.LocationClient$1@40554e10 that was originally bound here03-29 15:36:52.300: E/ActivityThread(6484): at android.app.LoadedApk$ServiceDispatcher.<init>(LoadedApk.java:938)03-29 15:36:52.300: E/ActivityThread(6484): at android.app.LoadedApk.getServiceDispatcher(LoadedApk.java:833)03-29 15:36:52.300: E/ActivityThread(6484): at android.app.ContextImpl.bindService(ContextImpl.java:864)03-29 15:36:52.300: E/ActivityThread(6484): at android.content.ContextWrapper.bindService(ContextWrapper.java:347)03-29 15:36:52.300: E/ActivityThread(6484): at com.baidu.location.LocationClient.for(Unknown Source)03-29 15:36:52.300: E/ActivityThread(6484): at com.baidu.location.LocationClient.goto(Unknown Source)03-29 15:36:52.300: E/ActivityThread(6484): at com.baidu.location.LocationClient$a.handleMessage(Unknown Source)03-29 15:36:52.300: E/ActivityThread(6484): at android.os.Handler.dispatchMessage(Handler.java:99)03-29 15:36:52.300: E/ActivityThread(6484): at android.os.Looper.loop(Looper.java:130)03-29 15:36:52.300: E/ActivityThread(6484): at android.app.ActivityThread.main(ActivityThread.java:3712)03-29 15:36:52.300: E/ActivityThread(6484): at java.lang.reflect.Method.invokeNative(Native Method)03-29 15:36:52.300: E/ActivityThread(6484): at java.lang.reflect.Method.invoke(Method.java:507)03-29 15:36:52.300: E/ActivityThread(6484): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:839)03-29 15:36:52.300: E/ActivityThread(6484): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:597)03-29 15:36:52.300: E/ActivityThread(6484): at dalvik.system.NativeStart.main(Native Method)

网上一查都说是没有stop 引起的，立马在activity上增加了以上代码：

@Override
    protected void onPause() {
        mMapView.onPause();
        super.onPause();
    }
    
    @Override
    protected void onResume() {
        mMapView.onResume();
        super.onResume();
    }
    
    @Override
    protected void onDestroy() {
    	//退出时销毁定位
        if (mLocClient != null)
        {
            mLocClient.stop();
        }
        mMapView.destroy();
        super.onDestroy();
    }
    
	@Override
    protected void onSaveInstanceState(Bundle outState) {
    	super.onSaveInstanceState(outState);
    	mMapView.onSaveInstanceState(outState);
    	
    }
    
    @Override
    protected void onRestoreInstanceState(Bundle savedInstanceState) {
    	super.onRestoreInstanceState(savedInstanceState);
    	mMapView.onRestoreInstanceState(savedInstanceState);
    }
    
    @Override
    public boolean onCreateOptionsMenu(Menu menu) {
//        getMenuInflater().inflate(R.menu.activity_main, menu);
        return true;
    }

再次运行程序，错误还是出现，苦恼了好几天，终于在网上 http://my.oschina.net/zhibuji/blog/91003找到了灵感，原来参考例子的时候忘了在AndroidManifest.xml中增加服务。

在该文件的<application/>节点中增加以下代码：

<service 
    android:name="com.baidu.location.f" 
    android:enabled="true"
    android:process=":remote" 
    android:permission="android.permission.BAIDU_LOCATION_SERVICE">
    <intent-filter>
        <action android:name="com.baidu.location.service_v2.6"></action>
    </intent-filter>
</service>

再次运行程序，成功解决问题！