"free(): invalid pointer" when running on Ubuntu x86_64 and Node.js >= v20.12.0

[kraenhansen]

Note

If you're seeing "free(): invalid pointer" when running on Ubuntu x86_64, a valid workaround is downgrading Node.js to v20.11.1

Description

See for more information realm/realm-core#7604.

The coverage tests started crashing around March 26th, by the release of Node.js v20.12.0.

Here's an example of a failing run: https://github.com/realm/realm-js/actions/runs/8552406490/job/23433443919?pr=6587

There seem to be two issues:

• The crash itself, which originates from Core (see #7604)
• The npm run ci:coverage process exits cleanly, which is unexpected from a crash.

I've reproduced the crash on these Realm JS commits:

• 2796745 (Realm Core 14.5.1)
• e15db60 (Realm Core 13.26.0)
• 8968776 (Realm Core 13.25.1)
• 42651be (Realm Core 13.25.0)

Stacktrace & log output

free(): invalid pointer

[sync-by-unito]

➤ PM Bot commented:

Jira ticket: RJS-2790

[kraenhansen]

This might have been the cause: realm/realm-core#7434 🤞

[kraenhansen]

I've created realm/realm-core#7604 with more information on the root cause of this crash.

[kraenhansen]

Regarding the uncorrect exit code when the subprocess spawed by nyc crashes, I've found these issues and PR that I believe is related:

• Exit code not preserved on JS heap out of memory (134) from mocha istanbuljs/nyc#798
• Node v20: TypeError [ERR_INVALID_ARG_TYPE]: The "code" argument must be of type number. Received type string ('128SIGINT') istanbuljs/nyc#1535
• chore(deps): bump foreground-child from ^2.0.0 to ^3.0.0 istanbuljs/nyc#1546