Protect against API abuse.
authorsvenpanne@chromium.org <svenpanne@chromium.org@ce2b1a6d-e550-0410-aec6-3dcde31c8c00>
Wed, 16 Apr 2014 08:42:08 +0000 (08:42 +0000)
committersvenpanne@chromium.org <svenpanne@chromium.org@ce2b1a6d-e550-0410-aec6-3dcde31c8c00>
Wed, 16 Apr 2014 08:42:08 +0000 (08:42 +0000)
commit0422c426bf0559a7b261337265d26dd8231d3365
tree7ddf90389ee7b9395f29bd964a553b7a4ce62993
parent139be49fcf1e58cff6a743a577f3f72f330df240
Protect against API abuse.

This makes Chrome's --single-process work again, but the real solution
is to pass an Isolate explicitly and fixing things on the Chrome side
=> follow-up CLs.

R=ulan@chromium.org

Review URL: https://codereview.chromium.org/239513006

git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@20787 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
src/api.cc