gpt4 book ai didi

android - 解绑服务但不销毁它

转载 作者:太空宇宙 更新时间:2023-11-03 12:35:36 24 4
gpt4 key购买 nike

在这里,我想使用名为 deadreckoning service 的服务来更新我的 UI,当此 Activity 停止时,我希望保持服务继续工作,所以我没有使用 unbind 方法,问题是,每次我销毁 fragment 时没有解除绑定(bind)方法的 UI,Logcat 给出错误,这是我的内存泄漏,实际上我在其他地方定义了 stopService,那么我该如何消除这个错误?我需要在绑定(bind)方法中放置一个预定义标志而不是 0 吗?以下是我的绑定(bind)代码:

    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 时,当用户按下停止按钮时,调用停止服务,通信和 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.<init>(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)

最佳答案

绑定(bind)前使用startService

关于android - 解绑服务但不销毁它,我们在Stack Overflow上找到一个类似的问题: https://stackoverflow.com/questions/20655784/

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