This adds a "killed tab" page and pages reload when killed on ChromeOS

chrome/browser/ui/browser.cc

Index: chrome/browser/ui/browser.cc
diff --git a/chrome/browser/ui/browser.cc b/chrome/browser/ui/browser.cc
index bed9899b6c1de53de5a6a2e32898c40a4ca35f35..33b396ef375aaf15c1a3479aafac9a64b564fc7d 100644
--- a/chrome/browser/ui/browser.cc
+++ b/chrome/browser/ui/browser.cc
@@ -2626,6 +2626,17 @@ void Browser::TabSelectedAt(TabContentsWrapper* old_contents,
                             bool user_gesture) {
   DCHECK(old_contents != new_contents);
 
+#if defined(OS_CHROMEOS)

[brettw, 2011/01/12 07:22:58]

This kind of thing in browser.cc gives Ben hives and makes me sad too. Can you
think of a way to avoid putting this in a global platform-independent file? We
can check with Ben tomorrow to see if he has a preferred way to do this.

[Ben Goodger (Google), 2011/01/12 15:34:11]

There are a couple of approaches here I can think of.

One would be if it seems like this feature may make it into non-ChromeOS Chrome
at some point, it should be behind a flag then that ChromeOS can default-on.
Then the code can just live here. It is possible that with future tabstrip
designs where we accumulate an infinite number of tabs that we will want this
behavior everywhere.

Alternatively ChromeOS could define its own TabStripModelObserver. This is more
applicable if there are or will be other ChromeOS ifdefs in the
TabStripModelObserver implementation.

+  // On ChromeOS, we want to automatically reload tabs that are killed
+  // when the user selects them.
+  if (user_gesture &&
+      new_contents->tab_contents()->crashed_status() ==
+      base::TERMINATION_STATUS_PROCESS_WAS_KILLED) {
+    Reload(CURRENT_TAB);
+    return;
+  }
+#endif
+
   // If we have any update pending, do it now.
   if (!chrome_updater_factory_.empty() && old_contents)
     ProcessPendingUIUpdates();