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 ?
Asked
Active
Viewed 2.0k times
11
Pankaj
- 7,908
- 6
- 42
- 65
BlackberryChennai
- 436
- 1
- 5
- 18
-
How can we be expected to help you without seeing any error logs or code? We can't simply divine what is wrong with your code – slayton Apr 05 '12 at 15:48
-
My question is: is this ok to get this in the logs... I mean is it something that can be ignored? The logs say - 03-16 15:17:24.233 W/ActivityManager( 1628): Launch timeout has expired, giving up wake lock! 03-16 15:17:24.273 W/ActivityManager( 1628): Activity idle timeout for HistoryRecord{40632cf8 – BlackberryChennai Apr 05 '12 at 15:51
1 Answers
14
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.
Source : Google Groups
BlackberryChennai
- 436
- 1
- 5
- 18
-
4Nopes, it's not just warning but in case you are running this application in lower device it may cause to struggle with your device and unfortunately restart device subsequently. – Suresh Sharma May 02 '14 at 06:14