Revert of Re-land: cc: Use worker context for one-copy tile initialization.

Revert of Re-land: cc: Use worker context for one-copy tile initialization. (patchset #33 id:630001 of https://codereview.chromium.org/1230203007/ )

Reason for revert:
This CL is responsible for issue 525811. Pixel 2015 gets strange artifacts across suspend/resume that only go away when you reboot.

Original issue's description:
> Re-land: cc: Use worker context for one-copy tile initialization.
> 
> This moves management of staging resources to
> OneCopyTileTaskWorkerPool class. This makes it possible
> to use a worker context to issue and detect when copy
> operations complete.
> 
> BUG=490295
> TBR=jamesr@chromium.org
> CQ_INCLUDE_TRYBOTS=tryserver.blink:linux_blink_rel
> 
> Committed: https://crrev.com/91d23278a61f82e03bf4bac2a5c509579a57edd0
> Cr-Commit-Position: refs/heads/master@{#344490}

TBR=jamesr@chromium.org,kbr@chromium.org,piman@chromium.org,primiano@chromium.org,sky@chromium.org,vmiura@chromium.org,vmpstr@chromium.org,reveman@chromium.org
NOPRESUBMIT=true
NOTREECHECKS=true
NOTRY=true
BUG=490295

[Eric Caruso, 2015-09-10 21:10:18]

Created Revert of Re-land: cc: Use worker context for one-copy tile
initialization.

[commit-bot: I haz the power, 2015-09-10 21:11:38]

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

[commit-bot: I haz the power, 2015-09-10 21:11:39]

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

[commit-bot: I haz the power, 2015-09-10 21:11:39]

No L-G-T-M from a valid reviewer yet. Only full committers are accepted.
Even if an L-G-T-M may have been provided, it was from a non-committer,
_not_ a full super star committer.
See http://www.chromium.org/getting-involved/become-a-committer
Note that this has nothing to do with OWNERS files.

[Ken Russell (switch to Gerrit), 2015-09-10 21:28:51]

While Chromium's policy is certainly to revert CLs that caused breakage, this
one landed 3 weeks ago and I'm concerned that dependent changes have landed
since then. Have you contacted the patch author directly?

[reveman, 2015-09-11 13:17:48]

On 2015/09/10 at 21:28:51, kbr wrote:
> While Chromium's policy is certainly to revert CLs that caused breakage, this
one landed 3 weeks ago and I'm concerned that dependent changes have landed
since then. Have you contacted the patch author directly?

Sorry, we can't revert this. Android one-copy depends on it for good performance
and acceptable memory usage. One-copy was enabled on Android after this landed
and the alternative is async uploads which has been removed since
(https://codereview.chromium.org/1186393004). A number of changes that depend on
that has been landed since so we can't switch back to it at this point without
reverting 5+ patches in addition to the async upload removal patch.

I think we just need to figure out what broke and fix it. I suspect that this is
the same issue as crbug.com/523411. I have a Samus device and will help get this
solved.

[Primiano Tucci (use gerrit), 2015-10-06 16:07:58]

Can this be closed? Keeps showing on rietveld and I think the chances that this
would apply cleanly after ~4 weeks are nearly zero.

[Primiano Tucci (use gerrit), 2015-10-06 16:07:59]

Can this be closed? Keeps showing on rietveld and I think the chances that this
would apply cleanly after ~4 weeks are nearly zero.

[Eric Caruso, 2015-10-06 17:25:43]

On 2015/10/06 16:07:59, Primiano Tucci wrote:
> Can this be closed? Keeps showing on rietveld and I think the chances that
this
> would apply cleanly after ~4 weeks are nearly zero.

Done.