Failure with Node.js 24

Hi Marten! It seems there is an issue with Node.js 24: ```sh $ nvm use 24 Now using node v24.9.0 (npm v11.6.0) $ npm test > @fails-components/webtransport-workspace@1.4.2 test > npm run test:node && npm run test:node:http2 && npm run test:chromium && npm run test:chromium:http2:polyfill && npm run test:chromium:http2:ponyfill && npm run test:firefox:http2:polyfill && npm run test:firefox:http2:ponyfill && npm run test:webkit:http2:polyfill && npm run test:webkit:http2:ponyfill > @fails-components/webtransport-workspace@1.4.2 test:node > npm run test:node --workspace test > @fails-components/webtransport-tests@1.4.2 test:node > node index.js node http3 server ready bidirectional streams free(): invalid pointer Error cause mocha process Error: Command was killed with SIGABRT (Aborted): mocha --colors ./*.spec.js at makeError (file:///home/damien/git/socket.io/webtransport/node_modules/execa/lib/error.js:59:11) at handlePromise (file:///home/damien/git/socket.io/webtransport/node_modules/execa/index.js:119:26) at process.processTicksAndRejections (node:internal/process/task_queues:105:5) at async runTests (file:///home/damien/git/socket.io/webtransport/test/index.js:76:5) at async file:///home/damien/git/socket.io/webtransport/test/index.js:127:3 { shortMessage: 'Command was killed with SIGABRT (Aborted): mocha --colors ./*.spec.js', command: 'mocha --colors ./*.spec.js', escapedCommand: 'mocha --colors "./*.spec.js"', exitCode: undefined, signal: 'SIGABRT', signalDescription: 'Aborted', stdout: undefined, stderr: undefined, failed: true, timedOut: false, isCanceled: false, killed: false } npm error Lifecycle script `test:node` failed with error: npm error code 1 npm error path /home/damien/git/socket.io/webtransport/test npm error workspace @fails-components/webtransport-tests@1.4.2 npm error location /home/damien/git/socket.io/webtransport/test npm error command failed npm error command sh -c node index.js node http ``` Node.js 22 works fine though: ```sh $ nvm use 22 Now using node v22.18.0 (npm v10.9.3) $ npm test > @fails-components/webtransport-workspace@1.4.2 test > npm run test:node && npm run test:node:http2 && npm run test:chromium && npm run test:chromium:http2:polyfill && npm run test:chromium:http2:ponyfill && npm run test:firefox:http2:polyfill && npm run test:firefox:http2:ponyfill && npm run test:webkit:http2:polyfill && npm run test:webkit:http2:ponyfill > @fails-components/webtransport-workspace@1.4.2 test:node > npm run test:node --workspace test > @fails-components/webtransport-tests@1.4.2 test:node > node index.js node http3 server ready bidirectional streams ✔ sends and receives data over an outgoing bidirectional stream ✔ sends and receives data over an outgoing bidirectional stream including a zero length chunk ✔ sends and receives data over an outgoing bidirectional stream with big buffers ✔ sends and receives concurrently data over an outgoing bidirectional stream with big buffers (124ms [...] ``` I haven't been able to pinpoint the issue, it seems the exception is not thrown in the JS scope.