Fixing a problem, where a hung renderer process is not killed when navigating away

content/browser/renderer_host/render_widget_host_impl.h

Index: content/browser/renderer_host/render_widget_host_impl.h
diff --git a/content/browser/renderer_host/render_widget_host_impl.h b/content/browser/renderer_host/render_widget_host_impl.h
index ca16dbc5e4cde46ccce7b5342d846f2f953eb2dd..205e6b290323ff78b87e30ce9cfb0d642463ee41 100644
--- a/content/browser/renderer_host/render_widget_host_impl.h
+++ b/content/browser/renderer_host/render_widget_host_impl.h
@@ -414,6 +414,11 @@ class CONTENT_EXPORT RenderWidgetHostImpl : virtual public RenderWidgetHost,
   void SetShouldAutoResize(bool enable);
 
  protected:
+  // Expose increment/decrement of the in-flight event count, so
+  // RenderViewHostImpl can account for in-flight beforeunload/unload events.
+  int IncrementInFlightEventCount() { return ++in_flight_event_count_; }
+  int DecrementInFlightEventCount() { return --in_flight_event_count_; }

[Charlie Reis, 2012/04/06 22:34:14]

These are small enough to be inlined, so we should use unix_hacker_style().

http://www.chromium.org/developers/coding-style
"Google style strongly encourages (but does not mandate) unix_hacker style on
member functions that do so little work they're effectively free, such as
simple, non-virtual getters and setters. This is also the team position. Some
code uses CamelCase for everything; avoid writing patches just to convert these
functions to unix_hacker style, but try to use it in new code you write unless
there are encapsulation reasons why CamelCase would be much more appropriate."

[nasko, 2012/04/10 00:16:37]

Done.

+
   // The View associated with the RenderViewHost. The lifetime of this object
   // is associated with the lifetime of the Render process. If the Renderer
   // crashes, its View is destroyed and this pointer becomes NULL, even though