-
Notifications
You must be signed in to change notification settings - Fork 246
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
最新版本android.os.DeadObjectException #35
Labels
Comments
HermesEventBus的实现发现有2个问题:
|
我的处理是在HermesEventBus中添加unInit方法,退出前调用,手动从主进程中移除自己: |
你这个问题我要查一下。你如果有好的处理办法,可以提pr。 |
嗯,谢谢,帮忙看看哈,目前我是觉得有问题的,最简单的demo就能测出来的,对了方便留个QQ吗?方便交流一下
发自网易邮箱大师
在2017年05月08日 23:01,Xiaofei 写道:
你这个问题我要查一下。你如果有好的处理办法,可以提pr。
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.
|
@zongleilei 你好,这个问题怎么解决呢,我也是出现了DeadObjectException |
我后来没有用这个了
| |
雷
|
|
邮箱:[email protected]
|
签名由 网易邮箱大师 定制
在2017年12月20日 12:32,Tpnet 写道:
@zongleilei 你好,这个问题怎么解决呢,我也是出现了DeadObjectException
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
最新版本中在主进程启动service,子进程即使在退出前调用HermesEventBus.getDefault().destroy();然后杀死子进程(Process.killProcess(Process.myPid());)后,再启动子进程,主进程使用HermesEventBus post事件后仍然产生异常:android.os.DeadObjectException,调试发现是主进程持有已经dead的子进程service造成的,可在子进程退出前该怎么处理呢?
The text was updated successfully, but these errors were encountered: