android: Limit num renderer to service slots

content/browser/renderer_host/render_process_host_unittest.cc

Index: content/browser/renderer_host/render_process_host_unittest.cc
diff --git a/content/browser/renderer_host/render_process_host_unittest.cc b/content/browser/renderer_host/render_process_host_unittest.cc
index 3bc7a02e07665fefd1eb778972d6f2be38cb2f4d..a846c714b2d15978fdff482ab6db010f76491edb 100644
--- a/content/browser/renderer_host/render_process_host_unittest.cc
+++ b/content/browser/renderer_host/render_process_host_unittest.cc
@@ -70,10 +70,6 @@ TEST_F(RenderProcessHostUnitTest, NoRendererProcessLimitOnAndroid) {
   // Disable any overrides.
   RenderProcessHostImpl::SetMaxRendererProcessCount(0);
 
-  // Verify that by default the limit on Android returns max size_t.

[Jay Civelli, 2017/04/03 16:19:48]

Should we add a TODO to bring that test back if/when we address this bug more
appropriately?

[boliu, 2017/04/03 16:33:03]

I think this is a really dumb check and should not exist period. Why does it
matter what that "infinite" constant is? The code below already shows creating
more renderers than practical is still allowed.

[Jay Civelli, 2017/04/03 16:40:50]

Makes sense.

-  EXPECT_EQ(std::numeric_limits<size_t>::max(),
-      RenderProcessHostImpl::GetMaxRendererProcessCount());
-
   // Add a few dummy process hosts.
   ASSERT_NE(0u, kMaxRendererProcessCount);
   std::vector<std::unique_ptr<MockRenderProcessHost>> hosts;