Make sure GpuMemoryBufferImpl is unmapped on destruction.

Make sure GpuMemoryBufferImpl is unmapped on destruction.

BUG=475633
Committed: https://crrev.com/87389cc050cc98397d0de838036307c078147d59
Cr-Commit-Position: refs/heads/master@{#330782}

[dshwang, 2015-05-15 17:34:13]

dongseong.hwang@intel.com changed reviewers:
+ ccameron@chromium.org, reveman@chromium.org

[dshwang, 2015-05-15 17:34:13]

ccameron, could you review?

it's extracted from https://codereview.chromium.org/1134993003/ as reveman
requested because of unrelated change.

[reveman, 2015-05-15 21:24:57]

What's the reason for why we need to prevent this?

[dshwang, 2015-05-18 08:03:19]

On 2015/05/15 21:24:57, reveman wrote:
> What's the reason for why we need to prevent this?

There is not crucial reason but it looks make sense.
1. It means some clients didn't unmap while the GpuMemoryBuffer is deleted. We
don't want to allow the client use mapped memory after destruction.
2. In Android, ANativeWindow_release and ANativeWindow_unlockAndPost rely on
HAL. Some vendor might assume ANativeWindow_release must be called after
ANativeWindow_unlockAndPost

[reveman, 2015-05-18 16:43:24]

lgtm

[dshwang, 2015-05-19 10:18:45]

The CQ bit was checked by dongseong.hwang@intel.com

[commit-bot: I haz the power, 2015-05-19 10:18:55]

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

[commit-bot: I haz the power, 2015-05-19 10:24:58]

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

[commit-bot: I haz the power, 2015-05-19 10:24:59]

Try jobs failed on following builders:
  chromium_presubmit on tryserver.chromium.linux (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.linux/builders/chromium_presub...)

[dshwang, 2015-05-19 12:53:48]

The CQ bit was checked by dongseong.hwang@intel.com

[commit-bot: I haz the power, 2015-05-19 12:54:09]

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

[dshwang, 2015-05-19 12:54:10]

The CQ bit was unchecked by dongseong.hwang@intel.com

[dshwang, 2015-05-19 12:54:40]

On 2015/05/18 16:43:24, reveman wrote:
> lgtm

thank you for reviewing.

ccameron, could you review as content/ owner?

[dshwang, 2015-05-20 10:22:45]

dongseong.hwang@intel.com changed reviewers:
- ccameron@chromium.org

[dshwang, 2015-05-20 10:23:37]

dongseong.hwang@intel.com changed reviewers:
+ ccameron@chromium.org, sievers@chromium.org

[dshwang, 2015-05-20 10:23:37]

ccameron, sievers: could you review this simple CL as owner?

[no sievers, 2015-05-20 17:51:55]

lgtm

[dshwang, 2015-05-20 17:59:16]

The CQ bit was checked by dongseong.hwang@intel.com

[commit-bot: I haz the power, 2015-05-20 17:59:40]

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

[commit-bot: I haz the power, 2015-05-20 19:32:18]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2015-05-20 19:34:13]

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