title: Activity Idle Timeout for ActivityRecord
body: <p>So I have a strange problem, and I'm not entirely sure what all information I should provide, but I'll do my best -- just let me know if I need to add more info. I'm having an issue that when I finish my <code>Activity</code> and return to the previous <code>Activity</code> (or launch it with a new <code>Intent</code> -- the problem seems to be centered on finishing the <code>Activity</code>) the UI performance drops drastically for about six or seven seconds, then returns to normal.</p>
  
  <p>From <code>LogCat</code>, this warning appears consistently:</p>
  
  <pre><code>07-11 22:09:42.594: W/ActivityManager(292): Launch timeout has expired, giving up wake lock!
  07-11 22:09:42.601: W/ActivityManager(292): Activity idle timeout for ActivityRecord{42bf6e00 com.kcoppock.sudokubeta/com.kcoppock.sudoku.SudokuBoardActivity}
  </code></pre>
  
  <p>As soon as the activity times out, UI performance returns to normal. Until that point it is very sluggish. I have no code that I am aware of that could be blocking the main thread, and I've even gone so far as to comment out my entire <code>onPause()</code> method to see if it makes any difference, and it does not.</p>
  
  <p>The <code>Activity</code> does not spawn any background threads, does not perform any network activity, the only disk access it has is some accessing of <code>SharedPreferences</code>. The previous questions I've been able to locate are about idle timeouts for <code>HistoryRecord</code>, not <code>ActivityRecord</code>. </p>
  
  <p>Any ideas what would cause this? Or how I could go about determining what is blocking the UI thread, if that is what is happening?</p>
  
  <p><strong>EDIT</strong> : Okay, just tried commenting out <em>everything</em> except super.onCreate() and setContentView() -- the problem still persists. It doesn't occur with any other Activities but this one, but there's <strong>NOTHING TO</strong> this one. :/</p>