Descriptionscheduler: Don't run multiple tasks per batch in a nested run loop
If the scheduler is in a nested run loop, it mustn't run multiple tasks
per batch. This is because one of those tasks could be a call to
RunLoop::Quit(), which means we have to yield control back to the
message loop. Since we have no direct way of observing when Quit is
called, just limit the number of tasks per batch to 1 in nested run
loops.
BUG=444764
Committed: https://crrev.com/418ebef4953dba6f31d7b16d9b4d1565c8b22a83
Cr-Commit-Position: refs/heads/master@{#340133}
Patch Set 1 #Patch Set 2 : Rebased. #Patch Set 3 : Build fix. #
Messages
Total messages: 21 (10 generated)
|