Running the wasm_compile_fuzzer locally on x64 *sometimes* hits this error:


#
# Fatal error in ../../v8/src/wasm/wasm-memory.cc, line 124
# Debug check failed: allocated_address_space_ + allocation_length <= reserved_address_space_ (96796672 vs. 93650944).
#
#
#
AddressSanitizer:DEADLYSIGNAL
=================================================================
==149497==ERROR: AddressSanitizer: ILL on unknown address 0x7fbc0721ef08 (pc 0x7fbc0721ef08 bp 0x7ffd10967f70 sp 0x7ffd10967f70 T0)
SCARINESS: 10 (signal)
    #0 0x7fbc0721ef07 in v8::base::OS::Abort() v8/src/base/platform/platform-posix.cc:381:5
    #1 0x7fbc072100a1 in V8_Fatal(char const*, int, char const*, ...) v8/src/base/logging.cc:170:3
    #2 0x7fbc0720f7ce in v8::base::(anonymous namespace)::DefaultDcheckHandler(char const*, int, char const*) v8/src/base/logging.cc:56:3
    #3 0x7fbc0666005d in v8::internal::wasm::WasmMemoryTracker::RegisterAllocation(void*, unsigned long, void*, unsigned long) v8/src/wasm/wasm-memory.cc:123:3
    #4 0x7fbc06660ec2 in v8::internal::wasm::(anonymous namespace)::TryAllocateBackingStore(v8::internal::wasm::WasmMemoryTracker*, v8::internal::Heap*, unsigned long, bool, void**, unsigned long*) v8/src/wasm/wasm-memory.cc:72:19
    #5 0x7fbc06661fab in v8::internal::wasm::NewArrayBuffer(v8::internal::Isolate*, unsigned long, bool, v8::internal::SharedFlag) v8/src/wasm/wasm-memory.cc:255:13
    #6 0x7fbc06690094 in GrowMemoryBuffer v8/src/wasm/wasm-objects.cc:464:10
    #7 0x7fbc06690094 in v8::internal::WasmMemoryObject::Grow(v8::internal::Isolate*, v8::internal::Handle<v8::internal::WasmMemoryObject>, unsigned int) v8/src/wasm/wasm-objects.cc:571
    #8 0x7fbc06342468 in v8::internal::__RT_impl_Runtime_WasmGrowMemory(v8::internal::Arguments, v8::internal::Isolate*) v8/src/runtime/runtime-wasm.cc:85:48
    #9 0x7fbc06340ec9 in v8::internal::Runtime_WasmGrowMemory(int, v8::internal::Object**, v8::internal::Isolate*) v8/src/runtime/runtime-wasm.cc:71:1
    #10 0x7ee8d0d84223  (<unknown module>)
[...]

It is hard to reproduce, since just running the crashing input does not produce the error. It's probably the interplay with all the previously allocated wasm memories.

This might also happen in the wild without us noticing, since it's only DCHECKs. It might be worth temporarily turning them into CHECKs (should not be performance critical), and see if we get crash reports.