Revert of gpu: guarantee to match pending GBM buffer request to actual GBM handle

Revert of gpu: guarantee to match pending GBM buffer request to actual GBM handle (patchset #3 id:40001 of https://codereview.chromium.org/2878573002/ )

Reason for revert:
DCHECK triggers on tests in GpuProcessHost::CreateGpuMemoryBuffer

Original issue's description:
> gpu: guarantee to match pending GBM buffer request to actual GBM handle
> 
> This CL makes |gpu_proecess_host| select the right callback by GMB id, not
> brute-force FIFO. It becomes more stable code for the future change.
> e.g. reordering IPC for priotization
> 
> BUG=475633, 629521
> 
> Review-Url: https://codereview.chromium.org/2878573002
> Cr-Commit-Position: refs/heads/master@{#471116}
> Committed: https://chromium.googlesource.com/chromium/src/+/e17baa4e12ee81c41668d7ef07e08a1a8e096dc6

TBR=piman@chromium.org,dongseong.hwang@chromium.org,dongseong.hwang@intel.com
# Skipping CQ checks because original CL landed less than 1 days ago.
NOPRESUBMIT=true
NOTREECHECKS=true
NOTRY=true
BUG=475633, 629521
Review-Url: https://codereview.chromium.org/2879723003
Cr-Commit-Position: refs/heads/master@{#471272}
Committed: https://chromium.googlesource.com/chromium/src/+/136aeef2b359782047037a3147c8b2a8af6aceda

[jochen (gone - plz use gerrit), 2017-05-12 11:33:58]

The CQ bit was checked by jochen@chromium.org

[jochen (gone - plz use gerrit), 2017-05-12 11:33:58]

Created Revert of gpu: guarantee to match pending GBM buffer request to actual
GBM handle

[commit-bot: I haz the power, 2017-05-12 11:34:11]

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-05-12 11:34:33]

CQ is committing da patch.

Bot data: {"patchset_id": 1, "attempt_start_ts": 1494588838198880, "parent_rev":
"5f68976791d996c1c0770507e379bd8d24a678a5", "commit_rev":
"136aeef2b359782047037a3147c8b2a8af6aceda"}

[commit-bot: I haz the power, 2017-05-12 11:34:46]

Description was changed from

==========
Revert of gpu: guarantee to match pending GBM buffer request to actual GBM
handle (patchset #3 id:40001 of https://codereview.chromium.org/2878573002/ )

Reason for revert:
DCHECK triggers on tests in GpuProcessHost::CreateGpuMemoryBuffer

Original issue's description:
> gpu: guarantee to match pending GBM buffer request to actual GBM handle
> 
> This CL makes |gpu_proecess_host| select the right callback by GMB id, not
> brute-force FIFO. It becomes more stable code for the future change.
> e.g. reordering IPC for priotization
> 
> BUG=475633, 629521
> 
> Review-Url: https://codereview.chromium.org/2878573002
> Cr-Commit-Position: refs/heads/master@{#471116}
> Committed:
https://chromium.googlesource.com/chromium/src/+/e17baa4e12ee81c41668d7ef07e0...

TBR=piman@chromium.org,dongseong.hwang@chromium.org,dongseong.hwang@intel.com
# Skipping CQ checks because original CL landed less than 1 days ago.
NOPRESUBMIT=true
NOTREECHECKS=true
NOTRY=true
BUG=475633, 629521
==========

to

==========
Revert of gpu: guarantee to match pending GBM buffer request to actual GBM
handle (patchset #3 id:40001 of https://codereview.chromium.org/2878573002/ )

Reason for revert:
DCHECK triggers on tests in GpuProcessHost::CreateGpuMemoryBuffer

Original issue's description:
> gpu: guarantee to match pending GBM buffer request to actual GBM handle
> 
> This CL makes |gpu_proecess_host| select the right callback by GMB id, not
> brute-force FIFO. It becomes more stable code for the future change.
> e.g. reordering IPC for priotization
> 
> BUG=475633, 629521
> 
> Review-Url: https://codereview.chromium.org/2878573002
> Cr-Commit-Position: refs/heads/master@{#471116}
> Committed:
https://chromium.googlesource.com/chromium/src/+/e17baa4e12ee81c41668d7ef07e0...

TBR=piman@chromium.org,dongseong.hwang@chromium.org,dongseong.hwang@intel.com
# Skipping CQ checks because original CL landed less than 1 days ago.
NOPRESUBMIT=true
NOTREECHECKS=true
NOTRY=true
BUG=475633, 629521

Review-Url: https://codereview.chromium.org/2879723003
Cr-Commit-Position: refs/heads/master@{#471272}
Committed:
https://chromium.googlesource.com/chromium/src/+/136aeef2b359782047037a3147c8...
==========

[commit-bot: I haz the power, 2017-05-12 11:34:52]

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

[dshwang, 2017-05-12 21:37:25]

On 2017/05/12 11:34:52, commit-bot: I haz the power wrote:
> Committed patchset #1 (id:1) as
>
https://chromium.googlesource.com/chromium/src/+/136aeef2b359782047037a3147c8...

hi jochen, thank you for revert. Could you share stack trace or use case in
which the DCHECK failed?

[dshwang, 2017-05-15 23:27:13]

On 2017/05/12 21:37:25, dshwang wrote:
> On 2017/05/12 11:34:52, commit-bot: I haz the power wrote:
> > Committed patchset #1 (id:1) as
> >
>
https://chromium.googlesource.com/chromium/src/+/136aeef2b359782047037a3147c8...
> 
> hi jochen, thank you for revert. Could you share stack trace or use case in
> which the DCHECK failed?

Hi Jochen, could you point out what test failed? thank you.