android取消服务,android – 取消绑定服务但不破坏它

在这里,我想使用我的服务称为deadreckoning service来更新我的UI,当这个活动停止时,我想保持服务仍然有效,所以我没有使用unbind方法,问题是,每次我用UI销毁片段而不解开方法,Logcat给出的错误是我的内存泄漏,实际上我在其他地方定义了stopService,那么我怎么能消除这个错误呢？我需要在bind方法中放置一个预定义的标志而不是0吗？ Folling是我的绑定代码：

if (DeadReckoningService.isDeadReckoningStart) {

Intent intent = new Intent(getActivity(), DeadReckoningService.class);

getActivity().bindService(intent, connection, 0);

serviceUpdateUI.post(runnable);

}

谢谢你的回答,也许我没有很好地解释这个问题.

以下是对环境的一些附加说明：

实际上我首先在broadcastReceiver中使用startService来启动.

然后在Activity(RunFragment)中使用bindService与此后台服务进行通信并更新UI.

当我关闭这个runFragment时,我不想停止服务,我仍然想让它在后面登录.所以我只想让它停止与runFragment的通信,所以我不使用unbindService(因为它也会停止服务).在logcat的这一刻,我得到了我的记忆泄漏的错误信息.如何避免此错误信息是我想问的问题.

那我什么时候停止服务呢？当用户下次再次打开此runFragment时,当用户按下停止按钮,调用stopservice时,通信和UIupdate的内容结束.

以下是Logcat中的错误报告

01-17 10:34:58.422: E/ActivityThread(21666): Activity study.runtracker.RunActivity has leaked ServiceConnection study.runtracker.RunFragment$2@425d6828 that was originally bound here

01-17 10:34:58.422: E/ActivityThread(21666): android.app.ServiceConnectionLeaked: Activity study.runtracker.RunActivity has leaked ServiceConnection study.runtracker.RunFragment$2@425d6828 that was originally bound here

01-17 10:34:58.422: E/ActivityThread(21666): at android.app.LoadedApk$ServiceDispatcher.(LoadedApk.java:979)

01-17 10:34:58.422: E/ActivityThread(21666): at android.app.LoadedApk.getServiceDispatcher(LoadedApk.java:873)

01-17 10:34:58.422: E/ActivityThread(21666): at android.app.ContextImpl.bindServiceCommon(ContextImpl.java:1561)

01-17 10:34:58.422: E/ActivityThread(21666): at android.app.ContextImpl.bindService(ContextImpl.java:1544)

01-17 10:34:58.422: E/ActivityThread(21666): at android.content.ContextWrapper.bindService(ContextWrapper.java:517)

01-17 10:34:58.422: E/ActivityThread(21666): at study.runtracker.RunFragment.onStart(RunFragment.java:74)

01-17 10:34:58.422: E/ActivityThread(21666): at android.support.v4.app.Fragment.performStart(Fragment.java:1524)

01-17 10:34:58.422: E/ActivityThread(21666): at android.support.v4.app.FragmentManagerImpl.moveToState(FragmentManager.java:957)

01-17 10:34:58.422: E/ActivityThread(21666): at android.support.v4.app.FragmentManagerImpl.moveToState(FragmentManager.java:1104)

01-17 10:34:58.422: E/ActivityThread(21666): at android.support.v4.app.FragmentManagerImpl.moveToState(FragmentManager.java:1086)

01-17 10:34:58.422: E/ActivityThread(21666): at android.support.v4.app.FragmentManagerImpl.dispatchStart(FragmentManager.java:1889)

01-17 10:34:58.422: E/ActivityThread(21666): at android.support.v4.app.FragmentActivity.onStart(FragmentActivity.java:587)

01-17 10:34:58.422: E/ActivityThread(21666): at android.app.Instrumentation.callActivityOnStart(Instrumentation.java:1171)

01-17 10:34:58.422: E/ActivityThread(21666): at android.app.Activity.performStart(Activity.java:5241)

01-17 10:34:58.422: E/ActivityThread(21666): at android.app.Activity.performRestart(Activity.java:5297)

01-17 10:34:58.422: E/ActivityThread(21666): at android.app.Activity.performResume(Activity.java:5302)

01-17 10:34:58.422: E/ActivityThread(21666): at android.app.ActivityThread.performResumeActivity(ActivityThread.java:2778)

01-17 10:34:58.422: E/ActivityThread(21666): at android.app.ActivityThread.handleResumeActivity(ActivityThread.java:2817)

01-17 10:34:58.422: E/ActivityThread(21666): at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1238)

01-17 10:34:58.422: E/ActivityThread(21666): at android.os.Handler.dispatchMessage(Handler.java:102)

01-17 10:34:58.422: E/ActivityThread(21666): at android.os.Looper.loop(Looper.java:136)

01-17 10:34:58.422: E/ActivityThread(21666): at android.app.ActivityThread.main(ActivityThread.java:5017)

01-17 10:34:58.422: E/ActivityThread(21666): at java.lang.reflect.Method.invokeNative(Native Method)

01-17 10:34:58.422: E/ActivityThread(21666): at java.lang.reflect.Method.invoke(Method.java:515)

01-17 10:34:58.422: E/ActivityThread(21666): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:779)

01-17 10:34:58.422: E/ActivityThread(21666): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:595)

01-17 10:34:58.422: E/ActivityThread(21666): at dalvik.system.NativeStart.main(Native Method)

解决方法:

在绑定之前使用startService

标签：android,android-service,memory-leaks,bind

来源： https://codeday.me/bug/20190825/1717897.html