Switch profiler from isolates to threads

runtime/vm/dart.cc

Index: runtime/vm/dart.cc
diff --git a/runtime/vm/dart.cc b/runtime/vm/dart.cc
index fd0dd87560cfa9c2d18d5001e028c7f36c66258d..a40e6d961cd69d12d5b96f8cb7017be2b5888a4a 100644
--- a/runtime/vm/dart.cc
+++ b/runtime/vm/dart.cc
@@ -297,9 +297,6 @@ RawError* Dart::InitializeIsolate(const uint8_t* snapshot_buffer, void* data) {
     ObjectStore::Init(I);
   }
 
-  // Setup for profiling.
-  Profiler::InitProfilingForIsolate(I);

[Ivan Posva, 2015/10/28 08:27:47]

There is no equivalent needed because the fact that this thread is associated
with an isolate makes it profilable, correct?

How do we ensure that the profiler is ticking though?

[Cutch, 2015/10/28 14:39:18]

Correct.
I'm doing a pass now to ensure that the profiler is ticking threads and stops
ticking when a thread exists an isolate.

-
   const Error& error = Error::Handle(Object::Init(I));
   if (!error.IsNull()) {
     return error.raw();