Revert of Replacing allocate bitmap IPC messages with a new Mojo interface.

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}

[Jay Civelli, 2016-12-06 16:44:51]

The CQ bit was checked by jcivelli@chromium.org

[Jay Civelli, 2016-12-06 16:44:51]

Created Revert of Replacing allocate bitmap IPC messages with a new Mojo
interface.

[commit-bot: I haz the power, 2016-12-06 16:45:19]

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, 2016-12-06 17:44:28]

CQ is committing da patch.

Bot data: {"patchset_id": 1, "attempt_start_ts": 1481042691594250, "parent_rev":
"23342f799594962314b1add3089fa13e0283e3f7", "commit_rev":
"7159e32d75ec3ca4afeb63a0c15678befe75b05c"}

[commit-bot: I haz the power, 2016-12-06 17:44:53]

Description was changed from

==========
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
==========

to

==========
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
==========

[commit-bot: I haz the power, 2016-12-06 17:44:54]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2016-12-06 17:46:55]

Description was changed from

==========
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
==========

to

==========
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}
==========

[commit-bot: I haz the power, 2016-12-06 17:46:58]

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

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

A revert of this CL (patchset #1 id:1) has been created in
https://codereview.chromium.org/2549213005/ by jcivelli@chromium.org.

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