Repository navigation
12.9.0 is it a bug? #29243
Description
Activity
What flags, if any, did you pass to
./configure? Does this happen when running Node.js, while building it, or only with specific scripts?build script is here:
workspace=$(cd $(dirname $0) && pwd); ./configure --without-snapshot --prefix=$workspace/output make -j8 && make installthen write a script(/tmp/ddd.js):
const a = { b: 2 }; console.log(a);i run it with:
node /tmp/ddd.jsthen it core dump with message:
# # Fatal error in , line 0 # Check failed: (isolate_->embedded_blob()) != nullptr. # # # #FailureMessage Object: 0x7fff8e43f6e0 (core dumped)the core stack is:
Program terminated with signal SIGILL, Illegal instruction. #0 0x0000000000a560c7 in v8::base::OS::Abort() () [Current thread is 1 (Thread 0x7f4271ce9740 (LWP 73051))] (gdb) bt #0 0x0000000000a560c7 in v8::base::OS::Abort() () #1 0x000000000186d7f5 in V8_Fatal(char const*, ...) () #2 0x000000000110d3ff in v8::internal::Deserializer::VisitOffHeapTarget(v8::internal::Code, v8::internal::RelocInfo*) () #3 0x000000000110f83e in v8::internal::Deserializer::ReadCodeObjectBody(int, unsigned long) () #4 0x000000000110e989 in bool v8::internal::Deserializer::ReadData<v8::internal::FullMaybeObjectSlot>(v8::internal::FullMaybeObjectSlot, v8::internal::FullMaybeObjectSlot, int, unsigned long) () #5 0x000000000110e5f6 in v8::internal::Deserializer::ReadObject(int) () #6 0x000000000110edc8 in bool v8::internal::Deserializer::ReadData<v8::internal::FullMaybeObjectSlot>(v8::internal::FullMaybeObjectSlot, v8::internal::FullMaybeObjectSlot, int, unsigned long) () #7 0x0000000000dcb3f0 in v8::internal::Heap::IterateStrongRoots(v8::internal::RootVisitor*, v8::internal::VisitMode) () #8 0x000000000111afbf in v8::internal::StartupDeserializer::DeserializeInto(v8::internal::Isolate*) () #9 0x0000000000d8176e in v8::internal::Isolate::Init(v8::internal::ReadOnlyDeserializer*, v8::internal::StartupDeserializer*) () #10 0x000000000111a735 in v8::internal::Snapshot::Initialize(v8::internal::Isolate*) () #11 0x0000000000c5e674 in v8::Isolate::Initialize(v8::Isolate*, v8::Isolate::CreateParams const&) () #12 0x0000000000b2a8d6 in node::NodeMainInstance::NodeMainInstance(v8::Isolate::CreateParams*, uv_loop_s*, node::MultiIsolatePlatform*, std::vector<std::string, std::allocator<std::string> > const&, std::vector<std::string, std::allocator<std::string> > const&, std::vector<unsigned long, std::allocator<unsigned long> > const*) () #13 0x0000000000abd7e6 in node::Start(int, char**) () #14 0x00007f4271d0eb8e in __libc_start_main (main=0xa5ae80 <main>, argc=2, argv=0x7ffd2876fe08, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7ffd2876fdf8) at libc-start.c:289 #15 0x0000000000a5d509 in _start () at ../sysdeps/x86_64/start.S:118it will not task a core dump when i use node v12.6, but it takes a core dump at v12.9
/cc @joyeecheung
I can reproduce this on master, though
./configure --without-snapshot --without-node-snapshotworks fine. Maybe we should just add an implication here.- added 2 commits that reference this issue
on Sep 3, 2019 - added a commit that references this issue
on Jul 27, 2026
version: 12.9.0
gcc: 8.2
message: