cc: Set the max frames pending from the thread proxy.

cc/thread_proxy.cc

Index: cc/thread_proxy.cc
diff --git a/cc/thread_proxy.cc b/cc/thread_proxy.cc
index ab708613204ecbc672900ca71bdb6abdef33994b..278fd4c0be57cc6ba06be91ac85bf627c9665d4e 100644
--- a/cc/thread_proxy.cc
+++ b/cc/thread_proxy.cc
@@ -945,6 +945,11 @@ void ThreadProxy::initializeRendererOnImplThread(CompletionEvent* completion, bo
                 capabilities->usingSwapCompleteCallback);
     }
 
+    int maxFramesPending = FrameRateController::kDefaultMaxFramesPending;
+    if (m_layerTreeHostImpl->outputSurface()->Capabilities().has_parent_compositor)

[jamesr, 2013/01/08 00:18:39]

This line caused crashes on the win_aura bots (and potentially in production) -
if we get a non-null OutputSurface but BindToClient fails, *initializeSucceeded
will be false and m_layerTreeHostImpl->outputSurface() will be NULL, so this
explodes.  See https://code.google.com/p/chromium/issues/detail?id=168691

+        maxFramesPending = 1;
+    m_schedulerOnImplThread->setMaxFramesPending(maxFramesPending);
+
     completion->signal();
 }