WasmGC cumulative array allocations crash Node.js process with FATAL ERROR instead of trapping

### Version 24.2.0 ### Platform ```text Linux unknown387c76016c42.lan 6.19.14-108.fc42.x86_64 #1 SMP PREEMPT_DYNAMIC Thu May 21 18:06:59 UTC 2026 x86_64 GNU/Linux ``` ### Subsystem _No response_ ### What steps will reproduce the bug? 1. Save the attached `exhaust.wat` file 2. Compile: `wasm-tools parse exhaust.wat -o exhaust.wasm` 3. Run: `node test.js` 4. Process crashes with FATAL ERROR + core dump `exhaust.wat`: ```wat (module (type $arr (array (mut i64))) (type $holder (array (mut (ref null $arr)))) (func (export "exhaust") (param $count i32) (local $h (ref $holder)) (local $i i32) ;; parent array to hold all refs (prevents GC collection) (array.new_default $holder (local.get $count)) (local.set $h) (loop $loop ;; allocate ~1MB array (131072 x 8 bytes) (local.get $h) (local.get $i) (array.new_default $arr (i32.const 131072)) (array.set $holder) ;; i++ (local.get $i) (i32.const 1) (i32.add) (local.set $i) ;; loop while i < count (local.get $i) (local.get $count) (i32.lt_u) (br_if $loop) ) ) ) ``` `test.js`: ```js const fs = require('fs'); (async () => { const mod = await WebAssembly.compile(fs.readFileSync('exhaust.wasm')); const inst = await WebAssembly.instantiate(mod); console.log('Allocating 10,000 x 1MB...'); inst.exports.exhaust(10000); console.log('Survived (should not reach here)'); })(); ``` ### How often does it reproduce? Is there a required condition? Fully reproducible. ### What is the expected behavior? Why is that the expected behavior? The Wasm module should trap or throw a catchable JavaScript error on GC allocation failure, not crash the process with `abort()`. Linear memory already handles exhaustion gracefully (`memory.grow` returns -1), and the WasmGC spec allows implementations to "terminate that computation and report an embedder-specific error" on resource exhaustion. ### What do you see instead? Exit code…