mus-gpu: Fix a couple of issues with MojoGpuMemoryBufferManager.

mus-gpu: Fix a couple of issues with MojoGpuMemoryBufferManager.

. Make sure the weak pointer is checked and invalidated in the correct
  thread. To do this: initialize the weak pointer in the memory thread,
  so that it can then be used to create a callback in any thread. But
  make sure this callback is checked in the same memory thread.

. Take a connection to mojom::GpuService as an input to the constructor,
  instead of getting the connection from the service_manager. This will
  be necessary when the connections are created by InterfaceProvider
  instead of by Connector (when running in chrome-renderer).

BUG=643746
Committed: https://crrev.com/a43aec3076a466005383d7db0d6926951c6f1623
Cr-Commit-Position: refs/heads/master@{#433593}

[sadrul, 2016-11-20 06:53:08]

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

[commit-bot: I haz the power, 2016-11-20 06:53:15]

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-11-20 09:23:14]

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

[commit-bot: I haz the power, 2016-11-20 09:23:18]

Dry run: This issue passed the CQ dry run.

[sadrul, 2016-11-21 01:10:24]

Description was changed from

==========
mus-gpu: Fix a couple of issues with MojoGpuMemoryBufferManager.

...

BUG=643746
==========

to

==========
mus-gpu: Fix a couple of issues with MojoGpuMemoryBufferManager.

. Make sure the weak pointer is checked and invalidated in the correct
  thread. To do this: initialize the weak pointer in the memory thread,
  so that it can then be used to create a callback in any thread. But
  make sure this callback is checked in the same memory thread.

. Take a connection to mojom::GpuService as an input to the constructor,
  instead of getting the connection from the service_manager. This will
  be necessary when the connections are created by InterfaceProvider
  instead of by Connector (when running in chrome-renderer).

BUG=643746
==========

[sadrul, 2016-11-21 01:10:45]

sadrul@chromium.org changed reviewers:
+ sky@chromium.org

[sky, 2016-11-21 16:43:29]

LGTM

[sadrul, 2016-11-21 17:40:48]

The CQ bit was checked by sadrul@chromium.org

[commit-bot: I haz the power, 2016-11-21 17:41:15]

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-11-21 18:35:13]

CQ is committing da patch.

Bot data: {"patchset_id": 1, "attempt_start_ts": 1479750048205640, "parent_rev":
"b33323ff8eeab494c5439e802c15c2c46983fb16", "commit_rev":
"bdace13f5bac3b78e222c46202d1b0b4c80505e6"}

[commit-bot: I haz the power, 2016-11-21 18:35:42]

Description was changed from

==========
mus-gpu: Fix a couple of issues with MojoGpuMemoryBufferManager.

. Make sure the weak pointer is checked and invalidated in the correct
  thread. To do this: initialize the weak pointer in the memory thread,
  so that it can then be used to create a callback in any thread. But
  make sure this callback is checked in the same memory thread.

. Take a connection to mojom::GpuService as an input to the constructor,
  instead of getting the connection from the service_manager. This will
  be necessary when the connections are created by InterfaceProvider
  instead of by Connector (when running in chrome-renderer).

BUG=643746
==========

to

==========
mus-gpu: Fix a couple of issues with MojoGpuMemoryBufferManager.

. Make sure the weak pointer is checked and invalidated in the correct
  thread. To do this: initialize the weak pointer in the memory thread,
  so that it can then be used to create a callback in any thread. But
  make sure this callback is checked in the same memory thread.

. Take a connection to mojom::GpuService as an input to the constructor,
  instead of getting the connection from the service_manager. This will
  be necessary when the connections are created by InterfaceProvider
  instead of by Connector (when running in chrome-renderer).

BUG=643746
==========

[commit-bot: I haz the power, 2016-11-21 18:35:43]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2016-11-21 18:39:13]

Description was changed from

==========
mus-gpu: Fix a couple of issues with MojoGpuMemoryBufferManager.

. Make sure the weak pointer is checked and invalidated in the correct
  thread. To do this: initialize the weak pointer in the memory thread,
  so that it can then be used to create a callback in any thread. But
  make sure this callback is checked in the same memory thread.

. Take a connection to mojom::GpuService as an input to the constructor,
  instead of getting the connection from the service_manager. This will
  be necessary when the connections are created by InterfaceProvider
  instead of by Connector (when running in chrome-renderer).

BUG=643746
==========

to

==========
mus-gpu: Fix a couple of issues with MojoGpuMemoryBufferManager.

. Make sure the weak pointer is checked and invalidated in the correct
  thread. To do this: initialize the weak pointer in the memory thread,
  so that it can then be used to create a callback in any thread. But
  make sure this callback is checked in the same memory thread.

. Take a connection to mojom::GpuService as an input to the constructor,
  instead of getting the connection from the service_manager. This will
  be necessary when the connections are created by InterfaceProvider
  instead of by Connector (when running in chrome-renderer).

BUG=643746

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

[commit-bot: I haz the power, 2016-11-21 18:39:14]

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