Revert of content: Re-enable ChildDiscardableSharedMemoryManagerBrowserTest.LockMemory test.

Revert of content: Re-enable ChildDiscardableSharedMemoryManagerBrowserTest.LockMemory test. (patchset #1 id:1 of https://codereview.chromium.org/1033553003/)

Reason for revert:
Still flaky

Original issue's description:
> content: Re-enable ChildDiscardableSharedMemoryManagerBrowserTest.LockMemory test.
>
> BUG=
> TEST=content_browsertests --gtest_filter=ChildDiscardableSharedMemoryManagerBrowserTest.LockMemory
>
> Committed: https://crrev.com/98e563846f88a2df7107e170381a6a5e8bd4454b
> Cr-Commit-Position: refs/heads/master@{#322122}

TBR=avi@chromium.org
NOPRESUBMIT=true
NOTREECHECKS=true
NOTRY=true
BUG=

Committed: https://crrev.com/c08010e76b0f9c77c336810be25373b95c91d7bb
Cr-Commit-Position: refs/heads/master@{#322175}

[reveman, 2015-03-25 16:51:00]

Created Revert of content: Re-enable
ChildDiscardableSharedMemoryManagerBrowserTest.LockMemory test.

[commit-bot: I haz the power, 2015-03-25 16:51:20]

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

[Avi (use Gerrit), 2015-03-25 16:51:39]

lgtm

[commit-bot: I haz the power, 2015-03-25 16:52:06]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2015-03-25 16:52:54]

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

[James Cook, 2015-03-25 18:04:21]

On 2015/03/25 16:52:54, I haz the power (commit-bot) wrote:
> Patchset 1 (id:??) landed as
> https://crrev.com/c08010e76b0f9c77c336810be25373b95c91d7bb
> Cr-Commit-Position: refs/heads/master@{#322175}

Is there a bug for this issue?

I'm the chrome-on-chromeos gardener today and this test was reliably failing on
the cros_trunk bot, so I'd like to follow along. Here's the bot:
http://master.chrome.corp.google.com:8011/builders/cros%20trunk

[reveman, 2015-03-25 18:11:39]

On 2015/03/25 at 18:04:21, jamescook wrote:
> On 2015/03/25 16:52:54, I haz the power (commit-bot) wrote:
> > Patchset 1 (id:??) landed as
> > https://crrev.com/c08010e76b0f9c77c336810be25373b95c91d7bb
> > Cr-Commit-Position: refs/heads/master@{#322175}
> 
> Is there a bug for this issue?
> 
> I'm the chrome-on-chromeos gardener today and this test was reliably failing
on the cros_trunk bot, so I'd like to follow along. Here's the bot:
http://master.chrome.corp.google.com:8011/builders/cros%20trunk

crbug.com/459703, sorry it should have been in the BUG= field.