jochen@chromium.org 27f3cc1b9c 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 Review URL: https://codereview.chromium.org/469783002 git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@24052 ce2b1a6d-e550-0410-aec6-3dcde31c8c00		2014-09-18 21:07:50 +00:00
..
count-hosts.js	Changed copyright header from google inc. to v8 project authors.	2008-09-09 20:08:45 +00:00
lineprocessor.cc	Require V8 to be explicitly initialized before an Isolate is created	2014-09-18 21:07:50 +00:00
process.cc	Require V8 to be explicitly initialized before an Isolate is created	2014-09-18 21:07:50 +00:00
samples.gyp	Split out libplatform into a separate libary	2014-07-03 07:37:27 +00:00
shell.cc	Require V8 to be explicitly initialized before an Isolate is created	2014-09-18 21:07:50 +00:00