Worker: Fix cross-thread violations on ObjectProxy

Worker: Fix cross-thread violations on ObjectProxy

This CL fixes 2 cross-thread violation issues:

1) This passes ParentFrameTaskRunners from MessagingProxy on the main thread to
   ObjectProxy on the worker thread so that the object proxy can post a task to
   the main thread without accessing a pointer to the messaging proxy.

2) This stops InProcessWorkerObjectProxy on the worker thread from accessing
   Document on the main thread and removes getExecutionContext().

BUG=667310
Committed: https://crrev.com/a36ee3740ceb393c22500b5ef4e170aafd79c566
Cr-Commit-Position: refs/heads/master@{#437187}

[nhiroki, 2016-12-02 08:34:42]

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

[commit-bot: I haz the power, 2016-12-02 08:35:06]

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, 2016-12-02 08:59:20]

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

[commit-bot: I haz the power, 2016-12-02 08:59:20]

Dry run: Try jobs failed on following builders:
  cast_shell_linux on master.tryserver.chromium.linux (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.linux/builders/cast_shell_linu...)

[nhiroki, 2016-12-05 03:40:22]

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

[commit-bot: I haz the power, 2016-12-05 03:40:29]

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, 2016-12-05 04:15:21]

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

[commit-bot: I haz the power, 2016-12-05 04:15:22]

Dry run: Try jobs failed on following builders:
  android_n5x_swarming_rel on master.tryserver.chromium.android (JOB_FAILED,
https://build.chromium.org/p/tryserver.chromium.android/builders/android_n5x_...)

[nhiroki, 2016-12-05 05:42:34]

Description was changed from

==========
Worker: Clean up InProcessWorkerObjectProxy

BUG=n/a
==========

to

==========
Worker: Fix cross-thread violations on InProcessWorkerObjectProxy

This CL fixes 2 cross-thread violation issues:

1) This passes ParentFrameTaskRunners from InProcessWorkerMessagingProxy on the
   main thread to InProcessWorkerObjectProxy on the worker thread so that the
   object proxy no longer needs to access the messing proxy |m_messagingProxy|
   to post a task.

2) This stops InProcessWorkerObjectProxy on the worker thread from accessing
   Document on the main thread by removing getExecutionContext().

BUG=n/a
==========

[nhiroki, 2016-12-05 05:43:42]

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

[commit-bot: I haz the power, 2016-12-05 05:43:55]

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

[nhiroki, 2016-12-05 05:45:38]

Description was changed from

==========
Worker: Fix cross-thread violations on InProcessWorkerObjectProxy

This CL fixes 2 cross-thread violation issues:

1) This passes ParentFrameTaskRunners from InProcessWorkerMessagingProxy on the
   main thread to InProcessWorkerObjectProxy on the worker thread so that the
   object proxy no longer needs to access the messing proxy |m_messagingProxy|
   to post a task.

2) This stops InProcessWorkerObjectProxy on the worker thread from accessing
   Document on the main thread by removing getExecutionContext().

BUG=n/a
==========

to

==========
Worker: Fix cross-thread violations on InProcessWorkerObjectProxy

This CL fixes 2 cross-thread violation issues:

1) This passes ParentFrameTaskRunners from InProcessWorkerMessagingProxy on the
   main thread to InProcessWorkerObjectProxy on the worker thread so that the
   object proxy can post a task to the messaging proxy without accessing a raw
   pointer to the messaging proxy.

2) This stops InProcessWorkerObjectProxy on the worker thread from accessing
   Document on the main thread and removes getExecutionContext().

BUG=n/a
==========

[commit-bot: I haz the power, 2016-12-05 06:38:46]

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

[commit-bot: I haz the power, 2016-12-05 06:38:47]

Dry run: Try jobs failed on following builders:
  linux_chromium_asan_rel_ng on master.tryserver.chromium.linux (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.linux/builders/linux_chromium_...)

[nhiroki, 2016-12-05 07:30:00]

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

[commit-bot: I haz the power, 2016-12-05 07:30:14]

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, 2016-12-05 08:32:25]

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

[commit-bot: I haz the power, 2016-12-05 08:32:26]

Dry run: Try jobs failed on following builders:
  linux_chromium_rel_ng on master.tryserver.chromium.linux (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.linux/builders/linux_chromium_...)

[nhiroki, 2016-12-05 09:28:50]

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

[commit-bot: I haz the power, 2016-12-05 09:29:13]

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, 2016-12-05 10:48:17]

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

[commit-bot: I haz the power, 2016-12-05 10:48:18]

Dry run: Try jobs failed on following builders:
  linux_chromium_rel_ng on master.tryserver.chromium.linux (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.linux/builders/linux_chromium_...)

[nhiroki, 2016-12-06 04:22:31]

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

[commit-bot: I haz the power, 2016-12-06 04:22:42]

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

[nhiroki, 2016-12-06 10:41:38]

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

[nhiroki, 2016-12-06 10:41:57]

Patchset #9 (id:160001) has been deleted

[commit-bot: I haz the power, 2016-12-06 10:41:58]

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, 2016-12-06 11:48:30]

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

[commit-bot: I haz the power, 2016-12-06 11:48:31]

Dry run: Try jobs failed on following builders:
  mac_chromium_rel_ng on master.tryserver.chromium.mac (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.mac/builders/mac_chromium_rel_...)

[nhiroki, 2016-12-07 05:35:47]

Patchset #1 (id:1) has been deleted

[nhiroki, 2016-12-07 05:35:53]

Patchset #1 (id:20001) has been deleted

[nhiroki, 2016-12-07 07:44:48]

Patchset #1 (id:40001) has been deleted

[nhiroki, 2016-12-07 07:44:56]

Patchset #1 (id:60001) has been deleted

[nhiroki, 2016-12-07 07:45:08]

Patchset #1 (id:80001) has been deleted

[nhiroki, 2016-12-07 07:45:22]

Patchset #1 (id:100001) has been deleted

[nhiroki, 2016-12-07 07:57:37]

Description was changed from

==========
Worker: Fix cross-thread violations on InProcessWorkerObjectProxy

This CL fixes 2 cross-thread violation issues:

1) This passes ParentFrameTaskRunners from InProcessWorkerMessagingProxy on the
   main thread to InProcessWorkerObjectProxy on the worker thread so that the
   object proxy can post a task to the messaging proxy without accessing a raw
   pointer to the messaging proxy.

2) This stops InProcessWorkerObjectProxy on the worker thread from accessing
   Document on the main thread and removes getExecutionContext().

BUG=n/a
==========

to

==========
Worker: Fix cross-thread violations on ObjectProxy

This CL fixes 2 cross-thread violation issues:

1) This passes ParentFrameTaskRunners from MessagingProxy on the main thread to
   ObjectProxy on the worker thread so that the object proxy can post a task to
   the messaging proxy without accessing a pointer to the messaging proxy.

2) This stops InProcessWorkerObjectProxy on the worker thread from accessing
   Document on the main thread and removes getExecutionContext().

BUG=n/a
==========

[nhiroki, 2016-12-07 08:01:56]

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

[commit-bot: I haz the power, 2016-12-07 08:02:06]

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

[nhiroki, 2016-12-07 08:03:02]

Description was changed from

==========
Worker: Fix cross-thread violations on ObjectProxy

This CL fixes 2 cross-thread violation issues:

1) This passes ParentFrameTaskRunners from MessagingProxy on the main thread to
   ObjectProxy on the worker thread so that the object proxy can post a task to
   the messaging proxy without accessing a pointer to the messaging proxy.

2) This stops InProcessWorkerObjectProxy on the worker thread from accessing
   Document on the main thread and removes getExecutionContext().

BUG=n/a
==========

to

==========
Worker: Fix cross-thread violations on ObjectProxy

This CL fixes 2 cross-thread violation issues:

1) This passes ParentFrameTaskRunners from MessagingProxy on the main thread to
   ObjectProxy on the worker thread so that the object proxy can post a task to
   the messaging proxy without accessing a pointer to the messaging proxy.

2) This stops InProcessWorkerObjectProxy on the worker thread from accessing
   Document on the main thread and removes getExecutionContext().

BUG=n/a
==========

[nhiroki, 2016-12-07 08:03:09]

Patchset #1 (id:120001) has been deleted

[nhiroki, 2016-12-07 08:03:16]

Patchset #1 (id:140001) has been deleted

[nhiroki, 2016-12-07 08:03:23]

Patchset #1 (id:180001) has been deleted

[nhiroki, 2016-12-07 08:03:29]

Patchset #1 (id:200001) has been deleted

[nhiroki, 2016-12-07 08:03:37]

Patchset #1 (id:220001) has been deleted

[nhiroki, 2016-12-07 08:04:43]

Description was changed from

==========
Worker: Fix cross-thread violations on ObjectProxy

This CL fixes 2 cross-thread violation issues:

1) This passes ParentFrameTaskRunners from MessagingProxy on the main thread to
   ObjectProxy on the worker thread so that the object proxy can post a task to
   the messaging proxy without accessing a pointer to the messaging proxy.

2) This stops InProcessWorkerObjectProxy on the worker thread from accessing
   Document on the main thread and removes getExecutionContext().

BUG=n/a
==========

to

==========
Worker: Fix cross-thread violations on ObjectProxy

This CL fixes 2 cross-thread violation issues:

1) This passes ParentFrameTaskRunners from MessagingProxy on the main thread to
   ObjectProxy on the worker thread so that the object proxy can post a task to
   the messaging proxy without accessing a pointer to the messaging proxy.

2) This stops InProcessWorkerObjectProxy on the worker thread from accessing
   Document on the main thread and removes getExecutionContext().

BUG=667310
==========

[nhiroki, 2016-12-07 08:06:20]

Description was changed from

==========
Worker: Fix cross-thread violations on ObjectProxy

This CL fixes 2 cross-thread violation issues:

1) This passes ParentFrameTaskRunners from MessagingProxy on the main thread to
   ObjectProxy on the worker thread so that the object proxy can post a task to
   the messaging proxy without accessing a pointer to the messaging proxy.

2) This stops InProcessWorkerObjectProxy on the worker thread from accessing
   Document on the main thread and removes getExecutionContext().

BUG=667310
==========

to

==========
Worker: Fix cross-thread violations on ObjectProxy

This CL fixes 2 cross-thread violation issues:

1) This passes ParentFrameTaskRunners from MessagingProxy on the main thread to
   ObjectProxy on the worker thread so that the object proxy can post a task to
   the main thread without accessing a pointer to the messaging proxy.

2) This stops InProcessWorkerObjectProxy on the worker thread from accessing
   Document on the main thread and removes getExecutionContext().

BUG=667310
==========

[nhiroki, 2016-12-07 08:34:52]

nhiroki@chromium.org changed reviewers:
+ falken@chromium.org

[nhiroki, 2016-12-07 08:34:53]

PTAL, thanks!

[commit-bot: I haz the power, 2016-12-07 11:12:41]

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

[commit-bot: I haz the power, 2016-12-07 11:12:41]

Dry run: This issue passed the CQ dry run.

[falken, 2016-12-08 04:49:41]

lgtm

[nhiroki, 2016-12-08 05:13:14]

The CQ bit was checked by nhiroki@chromium.org

[commit-bot: I haz the power, 2016-12-08 05:13:36]

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, 2016-12-08 05:17:57]

CQ is committing da patch.

Bot data: {"patchset_id": 240001, "attempt_start_ts": 1481173994568010,
"parent_rev": "1625f7dca301abd197df778622a58c62a0682f18", "commit_rev":
"95214ef8329e3ad85f343d8e6b336d1a04e074cc"}

[commit-bot: I haz the power, 2016-12-08 05:18:47]

Committed patchset #1 (id:240001)

[commit-bot: I haz the power, 2016-12-08 05:20:57]

Description was changed from

==========
Worker: Fix cross-thread violations on ObjectProxy

This CL fixes 2 cross-thread violation issues:

1) This passes ParentFrameTaskRunners from MessagingProxy on the main thread to
   ObjectProxy on the worker thread so that the object proxy can post a task to
   the main thread without accessing a pointer to the messaging proxy.

2) This stops InProcessWorkerObjectProxy on the worker thread from accessing
   Document on the main thread and removes getExecutionContext().

BUG=667310
==========

to

==========
Worker: Fix cross-thread violations on ObjectProxy

This CL fixes 2 cross-thread violation issues:

1) This passes ParentFrameTaskRunners from MessagingProxy on the main thread to
   ObjectProxy on the worker thread so that the object proxy can post a task to
   the main thread without accessing a pointer to the messaging proxy.

2) This stops InProcessWorkerObjectProxy on the worker thread from accessing
   Document on the main thread and removes getExecutionContext().

BUG=667310

Committed: https://crrev.com/a36ee3740ceb393c22500b5ef4e170aafd79c566
Cr-Commit-Position: refs/heads/master@{#437187}
==========

[commit-bot: I haz the power, 2016-12-08 05:20:58]

Patchset 1 (id:??) landed as
https://crrev.com/a36ee3740ceb393c22500b5ef4e170aafd79c566
Cr-Commit-Position: refs/heads/master@{#437187}