Trigger the Snippets Scheduler when Resuming Activities

chrome/android/java/src/org/chromium/chrome/browser/init/AsyncInitializationActivity.java

Index: chrome/android/java/src/org/chromium/chrome/browser/init/AsyncInitializationActivity.java
diff --git a/chrome/android/java/src/org/chromium/chrome/browser/init/AsyncInitializationActivity.java b/chrome/android/java/src/org/chromium/chrome/browser/init/AsyncInitializationActivity.java
index 3653838554ba3620d69de5f5735247af2e725473..080a6b18bdd5190c9e79826cb53c7277a432c34a 100644
--- a/chrome/android/java/src/org/chromium/chrome/browser/init/AsyncInitializationActivity.java
+++ b/chrome/android/java/src/org/chromium/chrome/browser/init/AsyncInitializationActivity.java
@@ -63,6 +63,8 @@ public abstract class AsyncInitializationActivity extends AppCompatActivity impl
     private long mLastUserInteractionTime;
     private boolean mIsTablet;
     private boolean mHadWarmStart;
+    private boolean mIsWarmOnResume;
+    private boolean mFirstResume = true;

[Bernhard Bauer, 2017/01/05 16:32:53]

Can you document this member? Specifically, this states whether the _next_ call
to onResume() is going to be the first, not whether the most recent one was the
first.

[fhorschig, 2017/01/05 17:11:13]

Done.

 
     public AsyncInitializationActivity() {
         mHandler = new Handler();
@@ -294,6 +296,8 @@ public abstract class AsyncInitializationActivity extends AppCompatActivity impl
         super.onResume();
         mNativeInitializationController.onResume();
         if (mLaunchBehindWorkaround != null) mLaunchBehindWorkaround.onResume();
+        mIsWarmOnResume = !mFirstResume || hadWarmStart();
+        mFirstResume = false;
     }
 
     @Override
@@ -408,6 +412,15 @@ public abstract class AsyncInitializationActivity extends AppCompatActivity impl
         return mHadWarmStart;
     }
 
+    /**
+     * If the activity started warm or was at least resumed once, every following resume must be
+     * warm.

[Bernhard Bauer, 2017/01/05 16:32:53]

It seems this comment should go to where we calculate the value, not where we
document the contract.

Then can you be a bit more detailed here about what exactly warm means, and
under which circumstances? Something like, "Whether this activity was warm
(native library loaded and initialized) by the time it was last resumed. This is
useful to distinguish between the case where an already running instance of
Chrome is being brought back to the foreground from the case where Chrome is
started, in order to avoid contention on browser startup".

...And now that I think of it that way, couldn't we get the value in the same
way as hadWarmStart()? That is, in onResume() check whether the native library
is loaded and set the flag based on that. If you want to land this CL in time
for FF though, I'd be okay with trying that out in a followup.

[fhorschig, 2017/01/05 17:11:13]

Done.
Done. Thank you for the wording idea!

 
I think we had that and the problem was, that some cold cold starts take long
enough for the library to load. So technically, it would be cold but it warmed
up during the run.
I can verify this as follow up nonetheless. 

[Bernhard Bauer, 2017/01/05 17:19:45]

What do you mean by long enough? During which run?
That would be great, thanks!

[fhorschig, 2017/01/05 17:23:06]

The first run  (with first run experience) for example.
Should be cold, but wasn't.

+     * @return Whether the activity is warm in onResume.
+     */
+    public boolean isWarmOnResume() {
+        return mIsWarmOnResume;
+    }
+
     @Override
     public void onUserInteraction() {
         mLastUserInteractionTime = SystemClock.elapsedRealtime();