| Index: base/task_scheduler/sequence.h
|
| diff --git a/base/task_scheduler/sequence.h b/base/task_scheduler/sequence.h
|
| index a2791d4f9fe68929933ebae637453f65de51fb04..3fa037fa35888ce8223b7f4976a50a7884651585 100644
|
| --- a/base/task_scheduler/sequence.h
|
| +++ b/base/task_scheduler/sequence.h
|
| @@ -26,8 +26,8 @@ namespace internal {
|
| // Note: there is a known refcounted-ownership cycle in the Scheduler
|
| // architecture: Sequence -> Task -> TaskRunner -> Sequence -> ...
|
| // This is okay so long as the other owners of Sequence (PriorityQueue and
|
| -// SchedulerWorkerThread in alternance and
|
| -// SchedulerWorkerPoolImpl::SchedulerWorkerThreadDelegateImpl::GetWork()
|
| +// SchedulerWorker in alternation and
|
| +// SchedulerWorkerPoolImpl::SchedulerWorkerDelegateImpl::GetWork()
|
| // temporarily) keep running it (and taking Tasks from it as a result). A
|
| // dangling reference cycle would only occur should they release their reference
|
| // to it while it's not empty. In other words, it is only correct for them to
|
|
|