Check failed: GetProcessWidePtrComprCage()->IsReserved() (9.4.146.13, Debian 11)

91 views
Skip to first unread message

Thorsten

unread,
Sep 9, 2021, 7:58:21 AM9/9/21
to v8-users
Hi,

I'm using the following configuration:
$ cat args.gn 
is_debug = true
target_cpu = "x64"
use_goma = false
is_component_build = true
symbol_level = 1

under Debian 11 with Version 9.4.146.13.

Compilation was successful.

When running the unittests I get a crash (see callstack below). The same crash I also get under windows build with MSVC.

Is this something that should concern me?

Thanks!

[----------] 9 tests from BytecodeArrayBuilderTest
[ RUN      ] BytecodeArrayBuilderTest.AllBytecodesGenerated


#
# Fatal error in ../../src/init/isolate-allocator.cc, line 98
# Check failed: GetProcessWidePtrComprCage()->IsReserved().
#
#
#
#FailureMessage Object: 0x7ffd8b7fa620
==== C stack trace ===============================

    /home/industrial/V8Dev/v8/out/x64.debug/libv8_libbase.so(v8::base::debug::StackTrace::StackTrace()+0x13) [0x7f4c42195013]
    /home/industrial/V8Dev/v8/out/x64.debug/libv8_libplatform.so(+0x1716d) [0x7f4c4214a16d]
    /home/industrial/V8Dev/v8/out/x64.debug/libv8_libbase.so(V8_Fatal(char const*, int, char const*, ...)+0x153) [0x7f4c42178d83]
    /home/industrial/V8Dev/v8/out/x64.debug/libv8_for_testing.so(v8::internal::IsolateAllocator::IsolateAllocator()+0x12e) [0x7f4c43a9778e]
    /home/industrial/V8Dev/v8/out/x64.debug/libv8_for_testing.so(v8::internal::Isolate::New()+0x1c) [0x7f4c4388c97c]
    /home/industrial/V8Dev/v8/out/x64.debug/libv8_for_testing.so(v8::Isolate::New(v8::Isolate::CreateParams const&)+0xf) [0x7f4c435dc42f]
    ./unittests(+0x9400e7) [0x55eead4900e7]
    ./unittests(+0x857b91) [0x55eead3a7b91]
    ./unittests(+0xe5e803) [0x55eead9ae803]
    ./unittests(+0xe4cee7) [0x55eead99cee7]
    ./unittests(+0xe4d530) [0x55eead99d530]
    ./unittests(+0xe576b5) [0x55eead9a76b5]
    ./unittests(+0xe60294) [0x55eead9b0294]
    ./unittests(+0xe57221) [0x55eead9a7221]
    ./unittests(+0x92907a) [0x55eead47907a]
    /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xea) [0x7f4c418d2d0a]
    ./unittests(_start+0x2a) [0x55eeace0b0ea]
Trace/breakpoint trap

Thorsten

unread,
Oct 19, 2021, 6:54:15 AM10/19/21
to v8-users
Hi again,

any hints about "GetProcessWidePtrComprCage" would be helpful ...

Jakob Kummerow

unread,
Oct 19, 2021, 8:46:21 AM10/19/21
to v8-users
Most people on the team (as well as our build bots) build x64.debug builds on Debian regularly, so the fact that you're seeing failures there is surprising. You may have to investigate a bit. Looks like line 115 in isolate-allocator.cc should have created the reservation that the CHECK in line 137 is complaining about.

Maybe something is special about your system configuration, possibly related to large (4GB) virtual memory reservations? But even if that was the case, V8's code should already be checking for any failures...

Thorsten

unread,
Oct 20, 2021, 2:33:42 AM10/20/21
to v8-users
I've set "v8_enable_pointer_compression_shared_cage = false". The tests are working now.
Reply all
Reply to author
Forward
0 new messages