cc: Use compositor context for signal sync token callback.

cc: Use compositor context for signal sync token callback.

The signal sync token callback is run from an IPC message from the GPU
process. IPC messages are received on the thread a context is bound to;
for the worker context this is the main thread. This causes a data race
and a crash during compositor tear down.

Using the compositor context is fine because it is bound to the impl
thread, and it's safe to receive tile manager callbacks there.

R=ericrk@chromium.org,vmpstr@chromium.org
BUG=673434
CQ_INCLUDE_TRYBOTS=master.tryserver.blink:linux_trusty_blink_rel

Review-Url: https://codereview.chromium.org/2682023005
Cr-Commit-Position: refs/heads/master@{#449792}
Committed: https://chromium.googlesource.com/chromium/src/+/31c92fe8317757707c7c910c7d67bc04fb6938be

[sunnyps, 2017-02-09 03:50:09]

Description was changed from

==========
cc: Use compositor context for signal sync token callback.

The signal sync token callback is run from an IPC message from the GPU
process. IPC messages are received on the thread a context is bound to;
for the worker context this is the main thread. This causes a data race
and a crash during compositor tear down.

Using the compositor context is fine because it is bound to the impl
thread, and it's safe to receive tile manager callbacks there.

R=ericrk@chromium.org,vmpstr@chromium.org
BUG=673434
==========

to

==========
cc: Use compositor context for signal sync token callback.

The signal sync token callback is run from an IPC message from the GPU
process. IPC messages are received on the thread a context is bound to;
for the worker context this is the main thread. This causes a data race
and a crash during compositor tear down.

Using the compositor context is fine because it is bound to the impl
thread, and it's safe to receive tile manager callbacks there.

R=ericrk@chromium.org,vmpstr@chromium.org
BUG=673434
CQ_INCLUDE_TRYBOTS=master.tryserver.blink:linux_trusty_blink_rel
==========

[sunnyps, 2017-02-09 03:50:13]

The CQ bit was checked by sunnyps@chromium.org to run a CQ dry run

[sunnyps, 2017-02-09 03:50:38]

ptal

[commit-bot: I haz the power, 2017-02-09 03:50:56]

Dry run: CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[commit-bot: I haz the power, 2017-02-09 06:48:39]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2017-02-09 06:48:40]

Dry run: This issue passed the CQ dry run.

[ericrk, 2017-02-09 18:31:28]

thanks for catching this! LGTM

[vmpstr, 2017-02-09 18:49:45]

lgtm

[sunnyps, 2017-02-10 22:07:16]

The CQ bit was checked by sunnyps@chromium.org

[commit-bot: I haz the power, 2017-02-10 22:08:04]

CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[commit-bot: I haz the power, 2017-02-10 23:46:58]

CQ is committing da patch.

Bot data: {"patchset_id": 1, "attempt_start_ts": 1486764436983140, "parent_rev":
"f6ca2907e1f31f01920b4d3447030dd47bb8f211", "commit_rev":
"31c92fe8317757707c7c910c7d67bc04fb6938be"}

[commit-bot: I haz the power, 2017-02-10 23:47:36]

Description was changed from

==========
cc: Use compositor context for signal sync token callback.

The signal sync token callback is run from an IPC message from the GPU
process. IPC messages are received on the thread a context is bound to;
for the worker context this is the main thread. This causes a data race
and a crash during compositor tear down.

Using the compositor context is fine because it is bound to the impl
thread, and it's safe to receive tile manager callbacks there.

R=ericrk@chromium.org,vmpstr@chromium.org
BUG=673434
CQ_INCLUDE_TRYBOTS=master.tryserver.blink:linux_trusty_blink_rel
==========

to

==========
cc: Use compositor context for signal sync token callback.

The signal sync token callback is run from an IPC message from the GPU
process. IPC messages are received on the thread a context is bound to;
for the worker context this is the main thread. This causes a data race
and a crash during compositor tear down.

Using the compositor context is fine because it is bound to the impl
thread, and it's safe to receive tile manager callbacks there.

R=ericrk@chromium.org,vmpstr@chromium.org
BUG=673434
CQ_INCLUDE_TRYBOTS=master.tryserver.blink:linux_trusty_blink_rel

Review-Url: https://codereview.chromium.org/2682023005
Cr-Commit-Position: refs/heads/master@{#449792}
Committed:
https://chromium.googlesource.com/chromium/src/+/31c92fe8317757707c7c910c7d67...
==========

[commit-bot: I haz the power, 2017-02-10 23:47:44]

Committed patchset #1 (id:1) as
https://chromium.googlesource.com/chromium/src/+/31c92fe8317757707c7c910c7d67...