Shutdown Service Workers before the profile is destroyed

chrome/browser/profiles/profile.cc

Index: chrome/browser/profiles/profile.cc
diff --git a/chrome/browser/profiles/profile.cc b/chrome/browser/profiles/profile.cc
index 72180132ccdc4001aeee81d8fbfabe7e6a66d4f2..f57decdc2f4ff8c68a4af47d201ae6629bd9ff3c 100644
--- a/chrome/browser/profiles/profile.cc
+++ b/chrome/browser/profiles/profile.cc
@@ -252,6 +252,8 @@ bool Profile::IsSyncAccessible() {
 void Profile::MaybeSendDestroyedNotification() {
   if (!sent_destroyed_notification_) {
     sent_destroyed_notification_ = true;
+
+    NotifyWillBeDestroyed(this);

[jam, 2014/10/23 22:45:22]

we shouldn't have content depend on every embedder knowing to do this or else
something in content (SW) breaks. can you find another way of initiating this
from within content?

[falken, 2014/10/24 00:53:34]

It's actually chrome stuff that's breaking because it expects the Profiles to
outlive RPHs (this particular crash is in ExtensionService). The current code
already depends on chrome shutting down Service Workers in BrowserProcessImpl to
prevent DCHECKs in chrome. This patch moves that special shutdown code to a
place that works for incognito profiles too.

It seems SW needs some signal from the embedder that it's time to shutdown.
Another option may be to change chrome's assumptions about RPH lifetimes, but
I'm not sure how involved that is.

     content::NotificationService::current()->Notify(
         chrome::NOTIFICATION_PROFILE_DESTROYED,
         content::Source<Profile>(this),