title: AsyncTasks will not fire until I leave an Activity
body: <p>I don't get this, and it's really frustrating me.</p>
  
  <p>All of my long-running operations happen in <code>AsyncTask</code>s.  For example, the user interacts with the app somehow and an item is added to a list.  This causes an <code>AsyncTask</code> to fire, the data to be written to an sqlite3 database, and then the list is refreshed.</p>
  
  <p>I've recently bumped my Android support up from 2.3.3 to 4.0.  I've created a new 4.0 emulator and, for some reason, all of my <code>AsyncTask</code>s seem to queue up and only fire once the user leaves the screen!</p>
  
  <p>Why is this happening????</p>
  
  <p>The code is pretty simple.  I'm not doing anything interesting here.  For example, here's an <code>AsyncTask</code> fire example:</p>
  
  <pre><code>Log log = data.mFoodLog;
  log.setUserId(getUserId());
  log.setDay(mBeginningOfToday.getTimeInMillis()/1000);
  log.setStatus(DbDefinitions.STATE_POSTING);
  
  (new SaveLogTask()).execute(new SaveObjectTaskParams(getApplicationContext(), log));
  </code></pre>
  
  <p>The debugger shows this code being executed.  I have another breakpoint inside the <code>doInBackground()</code> method, but that breakpoint never gets hit until I leave the screen.  I've also put <code>Log.e</code> messages around this code and ran it without the debugger to make sure the debugger isn't doing anything weird.  <code>doInBackground()</code> <strong>never</strong> gets fired until I leave the <code>Activity</code>.</p>