HistoryRecord 的活动空闲超时? [英] Activity idle timeout for HistoryRecord?

查看:18
本文介绍了HistoryRecord 的活动空闲超时?的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

W/ActivityManager(   81): Launch timeout has expired, giving up wake lock!
W/ActivityManager(   81): Activity idle timeout for HistoryRecord

有谁知道什么原因会导致这种情况发生?谢谢.

Does anyone know what reason would cause this happens? Thanks.

推荐答案

表示Activity无法显示,因为它仍在尝试完成执行;同时 ActivityManager 已超时.

It means that the Activity cannot be displayed because it is still trying to complete execution; meanwhile the ActivityManager has timed out.

我遇到了同样的问题,并通过整理 Activity 对象之间的依赖关系设法解决了这个问题.

I had the same problem, and managed to resolve it by tidying up dependencies between Activity objects.

我建议启动调试器.查看您的 Activity 所依赖的任何服务"(例如 http 客户端、解析器等)并检查它是否未阻塞.如果您有在 Activity 对象之间共享的服务",那么检查它们是否仍然存在于内存中可能也是值得的,因为 GC 可能已经破坏了任何静态引用的服务对象或缓存为 WeakReference 对象的对象.

I would recommend starting up the debugger. Look at any 'services' that your Activity depends on (e.g. http client, parsers etc.) and check that it is not blocking. If you have 'services' that are shared between Activity objects, it might also be worth checking that they still exist in memory as GC may have destroyed any statically referenced service objects or objects cached as WeakReference objects.

这篇关于HistoryRecord 的活动空闲超时?的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆