Add TextureMailboxDeleter to cc::Display.

Add TextureMailboxDeleter to cc::Display.

BUG=

Committed: https://crrev.com/e7002da73ea0a881bea02bab6781672ca3eeb7b4
Cr-Commit-Position: refs/heads/master@{#297289}

[jbauman, 2014-09-16 21:46:40]

jbauman@chromium.org changed reviewers:
+ jamesr@chromium.org

[jamesr, 2014-09-16 22:52:13]

Hmm, as I understand it TextureMailboxDeleter is a utility for handling
callbacks across different threads. But we only ever have cc::Display run on one
thread.  Do we need this complexity?

[jbauman, 2014-09-16 22:59:08]

On 2014/09/16 22:52:13, jamesr wrote:
> Hmm, as I understand it TextureMailboxDeleter is a utility for handling
> callbacks across different threads. But we only ever have cc::Display run on
one
> thread.  Do we need this complexity?

We'll need at least some of the complexity with the WeakPtrFactory to handle
deletion. I'm not sure that we'd need the full complexity of the multi-thread
stuff, but it already exists, and it would make the passing of the
CopyOutputResult across threads simpler.

[jbauman, 2014-09-25 22:32:31]

ping. Without this, a bunch of types of CopyOutputRequests DCHECK because they
can't create a release callback for their mailboxes.

[jamesr, 2014-09-29 21:53:30]

lgtm

This is unfortunately heavyweight for this use case, but we can optimize later.

[jbauman, 2014-09-29 21:55:00]

The CQ bit was checked by jbauman@chromium.org

[commit-bot: I haz the power, 2014-09-29 21:56:04]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/580593002/1

[commit-bot: I haz the power, 2014-09-29 22:39:21]

Committed patchset #1 (id:1) as d696b75ec57aa15245f8dcfda1bf8b2736639a92

[commit-bot: I haz the power, 2014-09-29 22:40:49]

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