More debugging for bug 17721767

Narrow down why GEL is being resumed instead of the top stack.

Change-Id: I79c0be4adf0ccee30e1a5aa4308ee91148f239fa
This commit is contained in:
Craig Mautner
2015-01-20 10:49:22 -08:00
parent 668cae1d47
commit 94ab46659b

View File

@@ -1478,7 +1478,7 @@ final class ActivityStack {
cancelInitializingActivities();
// Find the first activity that is not finishing.
ActivityRecord next = topRunningActivityLocked(null);
final ActivityRecord next = topRunningActivityLocked(null);
// Remember how we'll process this pause/resume situation, and ensure
// that the state is reset however we wind up proceeding.
@@ -1819,7 +1819,9 @@ final class ActivityStack {
EventLog.writeEvent(EventLogTags.AM_RESUME_ACTIVITY,
next.userId, System.identityHashCode(next),
next.task.taskId, next.shortComponentName);
next.task.taskId, next.shortComponentName + " top="
+ mStacks.get(mStacks.size() - 1).mStackId + " Callers="
+ Debug.getCallers(6));
next.sleeping = false;
mService.showAskCompatModeDialogLocked(next);