tag 79b917b43eed601712f750a9390190cc5af6e58d
tagger The Android Open Source Project <initial-contribution@android.com> Wed Jun 24 14:44:44 2015 -0700
object ed1882813d7c6b87543d8006a9d02aa55fef8b0d

Android 5.1.1 release 5

commit ed1882813d7c6b87543d8006a9d02aa55fef8b0d
author Brian Attwell <brianattwell@google.com> Wed Feb 11 14:12:41 2015 -0800
committer Brian Attwell <brianattwell@google.com> Wed Feb 11 23:09:55 2015 +0000
tree 024d950025572adda5e6f539698973e209e75ae4
parent f0a2a8b2f8b652ed251d96deec6e1d59ce693839

Don't access mRecentLoaderResults in background

Lists inside mRecentLoaderResults are cleared inside
Loader#onReset. Therefore, Retreiving items inside mRecentLoaderResults's
lists on a background thread can result in retreiving nulled out
ArrayList entries.

Fix:
* Only access mRecentLoaderResults on the main thread
* Don't crash when encountering null entries inside mRecentLoaderResults,
  in case I'm wrong about the reason these entries are null
  (although I can't see any other causes)
* make bindRecentData() sorting stable, since I'm already editing
  this code anyway

Bug: 19320314
Change-Id: Id871a8c0de3685baf07a6c4d65a4835380b1b99a