Make sure FrameScheduler is cleared when LocalFrame::detach() finishes

components/scheduler/child/single_thread_idle_task_runner.cc

Index: components/scheduler/child/single_thread_idle_task_runner.cc
diff --git a/components/scheduler/child/single_thread_idle_task_runner.cc b/components/scheduler/child/single_thread_idle_task_runner.cc
index e73adf543a12280f8e1863b03b8ccc6fd6cb6372..9b6bba38bfcc6e84df63a297dddc8d5c12b236ad 100644
--- a/components/scheduler/child/single_thread_idle_task_runner.cc
+++ b/components/scheduler/child/single_thread_idle_task_runner.cc
@@ -84,7 +84,7 @@ void SingleThreadIdleTaskRunner::RunTask(IdleTask idle_task) {
 
 void SingleThreadIdleTaskRunner::SetBlameContext(
     base::trace_event::BlameContext* blame_context) {
-  blame_context_ = blame_context;
+  blame_context_ = blame_context ? blame_context->weak_ptr() : nullptr;

[Primiano Tucci (use gerrit), 2016/06/10 07:50:35]

how do you know that here you are on the right thread (the one where
blame_context lives) so invoking weak_ptr() is safe?

[Xiaocheng, 2016/06/10 08:07:08]

Are you implying any potentially risky design?

In my understanding, it's currently safe. The only call site of
SingleThreadIdleTaskRunner::SetBlameContext() is in
RendererBlinkPlatformImpl::ctor(), which can only be run in the main thread. The
only BlameContext that can be passed to this function is the singleton
RendererBlinkPlatformImpl::top_level_blame_context_, which also live in the main
thread.

I can also add a DCHECK(thread_checker_.CalledOnValidThread()) in
BlameContext::weak_ptr() to make sure that it's called on the correct thread.

 }
 
 }  // namespace scheduler