Require V8 to be explicitly initialized before an Isolate is created

Require V8 to be explicitly initialized before an Isolate is created

We also initialize the Isolate on creation.

This should allow for getting rid of the last remaining default isolate
traces. Also, it'll speed up several isolate related operations that no
longer require locks.

Embedders that relied on v8::Isolate to return an uninitialized Isolate
(so they can set ResourceConstraints for example, or set flags that
modify the way the isolate is created) should either do the setup before
creating the isolate, or use the recently added CreateParams to pass e.g.
ResourceConstraints.

BUG=none
LOG=y
R=svenpanne@chromium.org

Committed: https://code.google.com/p/v8/source/detail?r=24052

[Sven Panne, 2014-09-02 13:31:12]

svenpanne@chromium.org changed reviewers:
+ svenpanne@chromium.org

[jochen (gone - plz use gerrit), 2014-09-17 11:57:01]

getting closer to passing all tests... still need to fix snapshot=off mode

[jochen (gone - plz use gerrit), 2014-09-18 12:38:33]

.... and we're there.

please review :)

[Sven Panne, 2014-09-18 13:21:41]

LGTM. Slowly things begin to look sane... :-)

[jochen (gone - plz use gerrit), 2014-09-18 21:08:24]

Committed patchset #5 (id:80001) manually as 24052 (presubmit successful).