Issue 2388 in v8: CHECK(isolate != __null) failed

[codesite...@google.com]

Status: New
Owner: ----

New issue 2388 by zd3...@gmail.com: CHECK(isolate != __null) failed
http://code.google.com/p/v8/issues/detail?id=2388

I have a C++ program that is using V8. I've been getting segfaults in the
V8 library so I built V8 with the following flags:

-DDEBUG
-DOBJECT_PRINT
-DVERIFY_HEAP
-DV8_ENABLE_CHECKS
-DENABLE_EXTRA_CHECKS
-DENABLE_DEBUGGER_SUPPORT

When I run the program with the debug-enabled build of the library I hit
this assertion failure:

#
# Fatal error in v8/src/isolate.h, line 442
# CHECK(isolate != __null) failed
#

This occurs on the very first V8 object instantiation:

HandleScope handle_scope;

I've attached stacktrace.txt which unfortunately only shows the assertion.

I have no idea what would cause
Thread::GetExistingThreadLocal(isolate_key_) to return null. Any help
would be appreciated!

Thanks,
Shawn

Attachments:
stacktrace.txt 1.1 KB

[codesite...@google.com]

Updates:
Status: Invalid

Comment #1 on issue 2388 by yan...@chromium.org: CHECK(isolate != __null)
failed
http://code.google.com/p/v8/issues/detail?id=2388

It appears that you don't have a default isolate. Usually, it is created by
the static initializer (v8::internal::StaticInitializer). Other than that,
please take shell.cc and d8.cc as examples how to embed V8.

Btw. this is not the right platform to discuss embedder issues as long as
they are confirmed to be bugs. Please use groups.google.com/group/v8-users

[codesite...@google.com]

Comment #2 on issue 2388 by zd3...@gmail.com: CHECK(isolate != __null)
failed
http://code.google.com/p/v8/issues/detail?id=2388

yangguo,

Thanks for the feedback. If I have further issues I'll post them in the
v8-users group. Sorry about that.

Shawn

[codesite...@google.com]

Comment #3 on issue 2388 by zd3...@gmail.com: CHECK(isolate != __null)
failed
http://code.google.com/p/v8/issues/detail?id=2388

BTW, turns out this was a threading issue. Needed to use v8::Locker.