[Session restore] Add MRU logic to loading of background pages.

chrome/browser/sessions/session_restore.cc

Index: chrome/browser/sessions/session_restore.cc
diff --git a/chrome/browser/sessions/session_restore.cc b/chrome/browser/sessions/session_restore.cc
index c6692162035c06fdb0cb02d7c1b7714f178e2d53..134397d09e0fc4d95941ac26bfc502f94d308a22 100644
--- a/chrome/browser/sessions/session_restore.cc
+++ b/chrome/browser/sessions/session_restore.cc
@@ -521,7 +521,8 @@ class SessionRestoreImpl : public content::NotificationObserver {
           continue;
 
         RestoredTab restored_tab(contents, is_selected_tab,
-                                 tab.extension_app_id.empty(), tab.pinned);
+                                 tab.extension_app_id.empty(), tab.pinned,
+                                 tab.last_activation_time);
         created_contents->push_back(restored_tab);
 
         // If this isn't the selected tab, there's nothing else to do.
@@ -545,7 +546,8 @@ class SessionRestoreImpl : public content::NotificationObserver {
             RestoreTab(tab, tab_index_offset + i, browser, false);
         if (contents) {
           RestoredTab restored_tab(contents, false,
-                                   tab.extension_app_id.empty(), tab.pinned);
+                                   tab.extension_app_id.empty(), tab.pinned,
+                                   tab.last_activation_time);
           created_contents->push_back(restored_tab);
         }
       }
@@ -591,6 +593,12 @@ class SessionRestoreImpl : public content::NotificationObserver {
     // focused tab will be loaded by Browser, and TabLoader will load the rest.
     DCHECK(web_contents->GetController().NeedsReload());
 
+    // Restore the saved activation time. By default, the activation time of a
+    // WebContent is initially set to the creation time of the tab, which is not
+    // necessarly the same as the loading time. This makes sure that the state
+    // is preserved between restores.
+    web_contents->SetLastActiveTime(tab.last_activation_time);

[sky, 2015/05/12 21:25:29]

It's my understanding there is no guarantee that timeticks increases across a
reboot. I suspect if you have your machine running for a long time, reboot, then
tab.last_activation_time could be very far in the future.

[Georges Khalil, 2015/05/15 16:55:30]

You are right, if the OS reboots, TimeTicks become irrelevant. Landed another CL
that changes WebContents::last_active_time to Time instead of TimeTicks. This
should fix it as we're using Time now. I also changed last_activation_time to
last_active_time for consistency with WebContents.

[sky, 2015/05/18 15:53:28]

I think time ticks is safer as blocks can go back. You just need to sanitize the
time ticks value when restoring.

[Georges Khalil, 2015/05/19 19:32:15]

I'm not sure how we could sanitize time ticks, as they're relative to the OS
session. The fact that the clock can change (daylight, for example), is not that
big of a deal, as we will still be able to order them correctly. And worst case,
the order won't be perfect, which is no worse than the original way of doing
things.

If you have a good way of sanitizing time ticks, that would be great (I'd have
to revert my TimeTicks==>Time patch, but not a big deal :) )

[sky, 2015/05/19 19:55:16]

After you've read the data in all we care about is relative order. You could
achieve this by sorting the original time ticks you read in, and assigning new
values based on sort position and current time ticks.

[gab, 2015/05/20 17:08:57]

I'm not convinced that this is true. For example, we could decide to stop
loading any tab whose latest timestamp is X days/hours behind the latest
shutdown.

I also agree with Georges that small order flips in tabs that have almost the
same timestamp but for which the clock has somehow jumped slightly backward and
introduced an ordering flip are mostly irrelevant.

+
     return web_contents;
   }