启动超时已过期，放弃唤醒锁！HistoryRecord 的活动空闲超时.这是需要担心的吗? [英] Launch timeout has expired, giving up wake lock! Activity idle timeout for HistoryRecord. Is this something to worry about?

问题描述

在我的应用程序中，我在 oncreate 中使用了 AsyncTask.有时我会在日志中看到启动超时已过期，放弃唤醒锁定！HistoryRecord 的活动空闲超时".这会导致任何问题吗，或者我们可以忽略这一点?

In my application I use AsyncTask in oncreate. Sometimes I get "Launch timeout has expired, giving up wake lock! Activity idle timeout for HistoryRecord" in the logs. Can this cause any issue, or we can just ignore this ?

推荐答案

终于找到答案了.这个可以忽略.

Finally Found the answer. This can be ignored.

这意味着您的主线程一直在运行，通过其消息队列泵送消息而不会闲置.如果那是您想要的，则没有什么可解决的.这就是日志消息是警告而不是错误的原因.

This means that your main thread is continually running, pumping message through its message queue without ever going idle. If that is what you want, there is nothing to fix. This is why the log message is a warning, not an error.

来源:Google 网上论坛

这篇关于启动超时已过期，放弃唤醒锁！HistoryRecord 的活动空闲超时.这是需要担心的吗?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！