Use loading tq instead of timer tq for per-isolate tasks

third_party/WebKit/Source/bindings/core/v8/V8Initializer.cpp

Index: third_party/WebKit/Source/bindings/core/v8/V8Initializer.cpp
diff --git a/third_party/WebKit/Source/bindings/core/v8/V8Initializer.cpp b/third_party/WebKit/Source/bindings/core/v8/V8Initializer.cpp
index 347c27bc822eeade5ec98a269aec2b81f2afe953..c6fb0b8bf409eba75fb11b89b8f5faab345f599e 100644
--- a/third_party/WebKit/Source/bindings/core/v8/V8Initializer.cpp
+++ b/third_party/WebKit/Source/bindings/core/v8/V8Initializer.cpp
@@ -394,8 +394,9 @@ void V8Initializer::initializeMainThread() {
 
   // NOTE: Some threads (namely utility threads) don't have a scheduler.
   WebScheduler* scheduler = Platform::current()->currentThread()->scheduler();
+  // TODO(altimin): Consider switching to timerTaskRunner here.

[haraken, 2017/01/18 00:05:03]

Add a comment and mention that we use a loading tq to prevent GC tasks from
being throttled.

   v8::Isolate* isolate = V8PerIsolateData::initialize(
-      scheduler ? scheduler->timerTaskRunner()
+      scheduler ? scheduler->loadingTaskRunner()

[haraken, 2017/01/18 00:05:03]

Maybe do we want to use an unthrottled task runner?

[altimin, 2017/01/18 13:07:09]

Most probably we need to expose different task runners to isolate and route
appropriate tasks to appropriate queues.

                 : Platform::current()->currentThread()->getWebTaskRunner());
 
   initializeV8Common(isolate);