Clear session-only data when all browser windows are closed.

chrome/browser/sessions/session_service_factory.cc

Index: chrome/browser/sessions/session_service_factory.cc
diff --git a/chrome/browser/sessions/session_service_factory.cc b/chrome/browser/sessions/session_service_factory.cc
index 05cf1989899cdad0688c324f4be690b59bd4ca9d..7e928f988db2fbbbae2c893d4ba1027a91131ee2 100644
--- a/chrome/browser/sessions/session_service_factory.cc
+++ b/chrome/browser/sessions/session_service_factory.cc
@@ -5,6 +5,7 @@
 #include "chrome/browser/sessions/session_service_factory.h"
 
 #include "chrome/browser/profiles/profile.h"
+#include "chrome/browser/sessions/session_data_deleter.h"
 #include "chrome/browser/sessions/session_service.h"
 #include "components/browser_context_keyed_service/browser_context_dependency_manager.h"
 
@@ -33,6 +34,8 @@ SessionService* SessionServiceFactory::GetForProfileIfExisting(
 
 // static
 void SessionServiceFactory::ShutdownForProfile(Profile* profile) {
+  DeleteSessionOnlyData(profile);

[benwells, 2013/10/15 08:28:51]

Why is this needed here?

[Sam McNally, 2013/10/15 22:53:05]

This is hit when doing a wrench menu quit. In that case the session service will
have been shut down before the browser windows close so the other case where
DeleteSessionOnlyData is called won't get hit.

In practice this won't do anything until wrench menu quit only closes browsers
so this could go in the cl that does that instead.

[benwells, 2013/10/15 22:58:41]

OK, that's what my theory was but wanted to get verification. Seems reasonable
to leave it in.

+
   // We're about to exit, force creation of the session service if it hasn't
   // been created yet. We do this to ensure session state matches the point in
   // time the user exited.