Reland of placing allocate bitmap IPC messages with a new Mojo interface.

Reland of placing allocate bitmap IPC messages with a new Mojo interface. (patchset #1 id:1 of https://codereview.chromium.org/2552913003/ )

Reason for revert:
The revert did not help with the crasher, so relanding this CL.

Original issue's description:
> Revert of Replacing allocate bitmap IPC messages with a new Mojo interface. (patchset #13 id:240001 of https://codereview.chromium.org/2488913003/ )
>
> Reason for revert:
> Might be causing a crasher on Windows.
> http://crbug.com/671459
>
> Original issue's description:
> > Replacing the AllocateBitmap related IPC messages with new mojo methods in the
> > RenderMessageFilter interface (it has to be part of the associated interface for
> > now because of ordering issue with other CC messages).
> >
> > As part of that, unified the bitmap allocation behavior in
> > ChildSharedBitmapManager on all platforms, by allocating shared memory
> > with the generic shared memory allocation code path and then
> > registering it as a bitmap.
> > Also moved ChildSharedBitmapManager from the ChildThreadImpl to RenderThreadImpl
> > as it is not common to all child processes.
> >
> > BUG=612500
> > TEST=content_shell should run normally with the --dissable-gpu flag.
> >
> > Committed: https://crrev.com/97235f8be07b5fe9200fe76901d27833325a5996
> > Cr-Commit-Position: refs/heads/master@{#436095}
>
> TBR=rockot@chromium.org,jbauman@chromium.org,kinuko@chromium.org,tsepez@chromium.org
> # Not skipping CQ checks because original CL landed more than 1 days ago.
> BUG=612500
>
> Committed: https://crrev.com/9a8e7d0071e6e2492a9f997c22238596ab4122dd
> Cr-Commit-Position: refs/heads/master@{#436629}

TBR=rockot@chromium.org,jbauman@chromium.org,kinuko@chromium.org,tsepez@chromium.org
# Not skipping CQ checks because original CL landed more than 1 days ago.
BUG=612500
Committed: https://crrev.com/0f21bd5836318170c155a0caf8bc6f81a939213d
Cr-Commit-Position: refs/heads/master@{#437064}

[Jay Civelli, 2016-12-07 19:35:27]

The CQ bit was checked by jcivelli@chromium.org

[Jay Civelli, 2016-12-07 19:35:28]

Created Reland of placing allocate bitmap IPC messages with a new Mojo
interface.

[commit-bot: I haz the power, 2016-12-07 19:35:59]

CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[Tom Sepez, 2016-12-07 19:39:33]

RS LGTM

[commit-bot: I haz the power, 2016-12-07 21:21:37]

CQ is committing da patch.

Bot data: {"patchset_id": 1, "attempt_start_ts": 1481139327826460, "parent_rev":
"2cdb8c33168434a61aec213e59ead29390f1154d", "commit_rev":
"40a60b42232d56e7391a83fb6916ab51623c46d7"}

[commit-bot: I haz the power, 2016-12-07 21:22:03]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2016-12-07 21:23:56]

Description was changed from

==========
Reland of placing allocate bitmap IPC messages with a new Mojo interface.
(patchset #1 id:1 of https://codereview.chromium.org/2552913003/ )

Reason for revert:
The revert did not help with the crasher, so relanding this CL.

Original issue's description:
> Revert of Replacing allocate bitmap IPC messages with a new Mojo interface.
(patchset #13 id:240001 of https://codereview.chromium.org/2488913003/ )
> 
> Reason for revert:
> Might be causing a crasher on Windows.
> http://crbug.com/671459
> 
> Original issue's description:
> > Replacing the AllocateBitmap related IPC messages with new mojo methods in
the
> > RenderMessageFilter interface (it has to be part of the associated interface
for
> > now because of ordering issue with other CC messages).
> >
> > As part of that, unified the bitmap allocation behavior in
> > ChildSharedBitmapManager on all platforms, by allocating shared memory
> > with the generic shared memory allocation code path and then
> > registering it as a bitmap.
> > Also moved ChildSharedBitmapManager from the ChildThreadImpl to
RenderThreadImpl
> > as it is not common to all child processes.
> >
> > BUG=612500
> > TEST=content_shell should run normally with the --dissable-gpu flag.
> >
> > Committed: https://crrev.com/97235f8be07b5fe9200fe76901d27833325a5996
> > Cr-Commit-Position: refs/heads/master@{#436095}
> 
>
TBR=rockot@chromium.org,jbauman@chromium.org,kinuko@chromium.org,tsepez@chrom...
> # Not skipping CQ checks because original CL landed more than 1 days ago.
> BUG=612500
> 
> Committed: https://crrev.com/9a8e7d0071e6e2492a9f997c22238596ab4122dd
> Cr-Commit-Position: refs/heads/master@{#436629}

TBR=rockot@chromium.org,jbauman@chromium.org,kinuko@chromium.org,tsepez@chrom...
# Not skipping CQ checks because original CL landed more than 1 days ago.
BUG=612500
==========

to

==========
Reland of placing allocate bitmap IPC messages with a new Mojo interface.
(patchset #1 id:1 of https://codereview.chromium.org/2552913003/ )

Reason for revert:
The revert did not help with the crasher, so relanding this CL.

Original issue's description:
> Revert of Replacing allocate bitmap IPC messages with a new Mojo interface.
(patchset #13 id:240001 of https://codereview.chromium.org/2488913003/ )
>
> Reason for revert:
> Might be causing a crasher on Windows.
> http://crbug.com/671459
>
> Original issue's description:
> > Replacing the AllocateBitmap related IPC messages with new mojo methods in
the
> > RenderMessageFilter interface (it has to be part of the associated interface
for
> > now because of ordering issue with other CC messages).
> >
> > As part of that, unified the bitmap allocation behavior in
> > ChildSharedBitmapManager on all platforms, by allocating shared memory
> > with the generic shared memory allocation code path and then
> > registering it as a bitmap.
> > Also moved ChildSharedBitmapManager from the ChildThreadImpl to
RenderThreadImpl
> > as it is not common to all child processes.
> >
> > BUG=612500
> > TEST=content_shell should run normally with the --dissable-gpu flag.
> >
> > Committed: https://crrev.com/97235f8be07b5fe9200fe76901d27833325a5996
> > Cr-Commit-Position: refs/heads/master@{#436095}
>
>
TBR=rockot@chromium.org,jbauman@chromium.org,kinuko@chromium.org,tsepez@chrom...
> # Not skipping CQ checks because original CL landed more than 1 days ago.
> BUG=612500
>
> Committed: https://crrev.com/9a8e7d0071e6e2492a9f997c22238596ab4122dd
> Cr-Commit-Position: refs/heads/master@{#436629}

TBR=rockot@chromium.org,jbauman@chromium.org,kinuko@chromium.org,tsepez@chrom...
# Not skipping CQ checks because original CL landed more than 1 days ago.
BUG=612500

Committed: https://crrev.com/0f21bd5836318170c155a0caf8bc6f81a939213d
Cr-Commit-Position: refs/heads/master@{#437064}
==========

[commit-bot: I haz the power, 2016-12-07 21:23:58]

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