Revert of Update V8 to version 4.3.10.

Revert of Update V8 to version 4.3.10. (patchset #1 id:1 of https://codereview.chromium.org/965873003/)

Reason for revert:
Speculative revert to see whether this affects some failing tests on linux:

http://build.chromium.org/p/chromium.linux/builders/Linux%20Tests%20%28dbg%29%281%29%2832%29

The two other Chromium commits in the narrowed-down range were reverted but that didn't help.

Original issue's description:
> Update V8 to version 4.3.10.
>
> Summary of changes available at:
> https://chromium.googlesource.com/v8/v8/+log/27a38796..627ffe9a
>
> Please follow these instructions for assigning/CC'ing issues:
> https://code.google.com/p/v8-wiki/wiki/TriagingIssues
>
> TBR=machenbach@chromium.org
>
> Committed: https://crrev.com/a4c7ab8af2530c04fb32939585d3b021aa7d9363
> Cr-Commit-Position: refs/heads/master@{#318556}

TBR=machenbach@chromium.org,v8-autoroll@chromium.org
NOPRESUBMIT=true
NOTREECHECKS=true
NOTRY=true

Committed: https://crrev.com/816e8760358a24ee2ddf5c748aa310caf4eab730
Cr-Commit-Position: refs/heads/master@{#318603}

[qyearsley, 2015-02-28 06:59:45]

Created Revert of Update V8 to version 4.3.10.

[commit-bot: I haz the power, 2015-02-28 07:00:46]

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

[commit-bot: I haz the power, 2015-02-28 07:01:09]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2015-02-28 07:01:47]

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

[Michael Achenbach, 2015-02-28 14:23:52]

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

The reason for reverting is: This revert also didn't help. Relanding. Maybe
something happened on these bots? The output of one test suggests to reinstall
the build deps:
http://build.chromium.org/p/chromium.linux/builders/Linux%20Tests%20%28dbg%29...

It's of course odd that this problem exists on different bots....