Remove the |max_threads| argument from CreateAndSetSimpleTaskScheduler().

remoting/client/jni/chromoting_jni_runtime.cc

Index: remoting/client/jni/chromoting_jni_runtime.cc
diff --git a/remoting/client/jni/chromoting_jni_runtime.cc b/remoting/client/jni/chromoting_jni_runtime.cc
index 201683ea6c0572ec8d7c8810fd77c4530c774bd3..4371c64f194278cb73d9cf0ccca27e305bc15399 100644
--- a/remoting/client/jni/chromoting_jni_runtime.cc
+++ b/remoting/client/jni/chromoting_jni_runtime.cc
@@ -43,9 +43,7 @@ bool RegisterChromotingJniRuntime(JNIEnv* env) {
 static void LoadNative(JNIEnv* env, const JavaParamRef<jclass>& clazz) {
   base::CommandLine::Init(0, nullptr);
 
-  // TODO(sergeyu): Consider adding separate pools for different task classes.
-  const int kMaxBackgroundThreads = 5;
-  base::TaskScheduler::CreateAndSetSimpleTaskScheduler(kMaxBackgroundThreads);
+  base::TaskScheduler::CreateAndSetSimpleTaskScheduler("RemotingJava");

[nicholss, 2017/03/17 17:20:54]

I have removed this file in https://codereview.chromium.org/2745583008/

It is now located: remoting/client/chromoting_client_runtime.cc

[fdoray, 2017/03/20 16:58:41]

Done.

 
   // Create the singleton now so that the Chromoting threads will be set up.
   remoting::ChromotingJniRuntime::GetInstance();