Always create FrameTreeNodes and RenderFrameHosts for every frame.

content/public/test/render_view_test.cc

Index: content/public/test/render_view_test.cc
diff --git a/content/public/test/render_view_test.cc b/content/public/test/render_view_test.cc
index 64a4d2c67ef9ba68db05a0d553dc3e634cc87123..b6066ec2d623f3fecf6f8a6487e28dd2a313b8af 100644
--- a/content/public/test/render_view_test.cc
+++ b/content/public/test/render_view_test.cc
@@ -41,6 +41,7 @@ const int32 kOpenerId = -2;
 const int32 kRouteId = 5;
 const int32 kMainFrameRouteId = 6;
 const int32 kNewWindowRouteId = 7;
+const int32 kNewFrameRouteId = 10;

[awong, 2013/12/27 21:59:36]

Is there a reason for 10? I would have expected 8 given the other routing ids
above are sequential (though it's odd that it starts at 5)

[nasko, 2013/12/27 22:14:53]

I'm not sure, since this came from Charlie's CL. I think it can potentially
catch issues where code expects sequential routing ids, which cannot be
guaranteed.

 const int32 kSurfaceId = 42;
 
 }  // namespace
@@ -140,6 +141,7 @@ void RenderViewTest::SetUp() {
   render_thread_->set_routing_id(kRouteId);
   render_thread_->set_surface_id(kSurfaceId);
   render_thread_->set_new_window_routing_id(kNewWindowRouteId);
+  render_thread_->set_new_frame_routing_id(kNewFrameRouteId);
 
   command_line_.reset(new CommandLine(CommandLine::NO_PROGRAM));
   params_.reset(new MainFunctionParams(*command_line_));