Remove the |max_threads| argument from CreateAndSetSimpleTaskScheduler().

remoting/host/setup/me2me_native_messaging_host_main.cc

Index: remoting/host/setup/me2me_native_messaging_host_main.cc
diff --git a/remoting/host/setup/me2me_native_messaging_host_main.cc b/remoting/host/setup/me2me_native_messaging_host_main.cc
index f94b2c5ea2c9292a7f82e3be99ae5c95c69cad22..adfe9cfcfab409f6ed0b153b4c7bc62f87025b20 100644
--- a/remoting/host/setup/me2me_native_messaging_host_main.cc
+++ b/remoting/host/setup/me2me_native_messaging_host_main.cc
@@ -86,9 +86,7 @@ int Me2MeNativeMessagingHostMain(int argc, char** argv) {
   // }
 #endif  // defined(REMOTING_ENABLE_BREAKPAD)
 
-  // TODO(sergeyu): Consider adding separate pools for different task classes.
-  const int kMaxBackgroundThreads = 5;
-  base::TaskScheduler::CreateAndSetSimpleTaskScheduler(kMaxBackgroundThreads);
+  base::TaskScheduler::CreateAndSetSimpleTaskScheduler("Me2Me");
 
   // Mac OS X requires that the main thread be a UI message loop in order to
   // receive distributed notifications from the System Preferences pane. An