Revert of Disable a test that fails under ASan and MSan

Revert of Disable a test that fails under ASan and MSan (patchset #1 id:1 of https://codereview.chromium.org/1007293002/)

Reason for revert:
This test is a victim of a bigger issue of main renderer message loop being used after it is deleted. Details are in crbug.com/467369.

I've also run the test with ASAN locally and didn't reproduce after a few runs.

Original issue's description:
> Disable a test that fails under ASan and MSan
>
> It can be flaky in other configurations as well
>
> BUG=467483
> TBR=nasko
>
> Committed: https://crrev.com/992ff715f61e90562983139ac31392b72e716822
> Cr-Commit-Position: refs/heads/master@{#320713}

TBR=timurrrr@chromium.org
NOPRESUBMIT=true
NOTREECHECKS=true
NOTRY=true
BUG=467483
Committed: https://crrev.com/216981c97018a8b8dea097cbde58889bf4e68c1a
Cr-Commit-Position: refs/heads/master@{#320755}

[nasko, 2015-03-16 18:23:16]

Created Revert of Disable a test that fails under ASan and MSan

[commit-bot: I haz the power, 2015-03-16 18:23:52]

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

[commit-bot: I haz the power, 2015-03-16 18:24:56]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2015-03-16 18:25:43]

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

[Timur Iskhodzhanov, 2015-03-17 10:55:24]

Don't approve.  [And I don't think this should have been TBR'ed]
We should not reenable the test [at least under MSan and ASan] as long as the
underlying issue is not fixed.

After this test got re-enabled, the MSan testers have turned red again and sent
out extra failure email notifications.

[Timur Iskhodzhanov, 2015-03-17 10:56:10]

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

The reason for reverting is: The underlying issue is still not fixed,
re-enabling the test causes bots to turn red.

Please wait for the underlying issue to be resolved before re-enabling..