Skip to content

Fatal error: Check failed: jit_page.has_value() with WebAssembly (PGlite) on v24.22.2 linux-x64 #67556

Open

Description

@jakedwyer

Version

v24.22.2 (actions/setup-node, linux-x64)

Platform

GitHub-hosted runner ubuntu-latest (Ubuntu 26.04 image 20261103.629), 2 vCPU, x64.

Subsystem

v8 / wasm

What steps will reproduce the bug?

Not reproducible on demand. A node --test run (process isolation, --test-concurrency=2, --test-randomize) aborted in one child process. That test file runs many in-process Postgres instances through @electric-sql/pglite 0.5.16 (Emscripten WebAssembly). A targeted rerun of 224 runs on the same runner image did not crash again (about 1 crash in 300 runs of that file).

How often does it reproduce? Is there a required condition?

Rarely: once in about 300 runs. No known required condition.

What is the expected behavior? Why is that the expected behavior?

The process should not abort.

What do you see instead?

# Fatal error in , line 0
# Check failed: jit_page.has_value().
#
#
#
#FailureMessage Object: 0x7ffccd5ab2e0
----- Native stack trace -----

 1: 0x9f06c1  [/opt/hostedtoolcache/node/24.22.2/x64/bin/node]
 2: 0x27e6c43 V8_Fatal(char const*, ...) [/opt/hostedtoolcache/node/24.22.2/x64/bin/node]
 3: 0xd95c19  [/opt/hostedtoolcache/node/24.22.2/x64/bin/node]
 4: 0x1904ab3  [/opt/hostedtoolcache/node/24.22.2/x64/bin/node]
 5: 0x193f50f  [/opt/hostedtoolcache/node/24.22.2/x64/bin/node]
 6: 0x19243ee  [/opt/hostedtoolcache/node/24.22.2/x64/bin/node]
 7: 0x19245a1  [/opt/hostedtoolcache/node/24.22.2/x64/bin/node]
 8: 0x18fc3ff  [/opt/hostedtoolcache/node/24.22.2/x64/bin/node]
 9: 0x18ff1fc  [/opt/hostedtoolcache/node/24.22.2/x64/bin/node]
10: 0x179432f  [/opt/hostedtoolcache/node/24.22.2/x64/bin/node]
11: 0x7b79a6e36d09 
✖ agent/lib/personal/isolation.test.ts (13641.072102ms)
✔ RED-1376: the people limit counts only new people, and the most senior are added first (5.542386ms)

Additional information

The process was a release build with no flags beyond --import tsx --test. Any guidance on V8 flags that would help narrow this down (for example, disabling memory protection keys for wasm code) is welcome.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions