GitLab

The constraints processing algorithm operates on data coming directly
from Blink, and it may happen that a future change accesses a
string or some other data that is allowed to be accessed only from
the main thread. So far no such bug has been found for device capture,
but one was recently discovered for screen capture. See
http://crbug.com/791992.

The original motivation to run constraints processing on the worker
thread was to avoid blocking the main thread in case the algorithm
took too long to run, but in practice we have not observed
significant performance issues.

Bug: 792106
Change-Id: I5fa6f9e1b107e680cb4a5b544488fe7f2d8bfb0d
Reviewed-on: https://chromium-review.googlesource.com/809011Reviewed-by: Henrik Boström <hbos@chromium.org>
Reviewed-by: Avi Drissman <avi@chromium.org>
Commit-Queue: Guido Urdaneta <guidou@chromium.org>
Cr-Commit-Position: refs/heads/master@{#521790}