Node v16 segfault on Jest 26/27 when using --detectOpenHandles

[milesj]

🐛 Bug Report

I've ran into this twice now while upgrade some projects. Here's some examples on Jest 26:

Beemo:

• Segfault: https://github.com/beemojs/beemo/runs/2751750475?check_suite_focus=true
• Build passes when I remove the options: https://github.com/beemojs/beemo/runs/2751795949?check_suite_focus=true

Boost:

• Open PR with a current segfault: deps: Audit 06/2021 milesj/boost#150

This also fails on Jest 27, example PR here: beemojs/beemo#137

To Reproduce

Clone and checkout this branch: milesj/boost#150 Setup with yarn install && yarn global add packemon && yarn run build.

Run yarn test on Node 16 to trigger the segfault. Can also run npx jest --detectOpenHandles.

Expected behavior

Doesnt segfault.

Link to repl or repo (highly encouraged)

• deps: Audit 06/2021 milesj/boost#150
• deps(jest): Update to v27. beemojs/beemo#137
• style: Switch to tabs from spaces. milesj/packemon#66

envinfo

  System:
    OS: macOS 11.2.3
    CPU: (12) x64 Intel(R) Core(TM) i7-9750H CPU @ 2.60GHz
  Binaries:
    Node: 16.3.0 - ~/.nvm/versions/node/v16.3.0/bin/node
    Yarn: 1.22.10 - ~/.nvm/versions/node/v16.3.0/bin/yarn
    npm: 7.15.1 - ~/.nvm/versions/node/v16.3.0/bin/npm

[thynson]

+1

[SimenB]

Prooobably nodejs/node#39019, fix should come in 16.4.0 (nodejs/node#39031)

[milesj]

Ok cool. At least I wasn't going crazy thinking it was my setup :P

[SimenB]

@milesj 16.4.0 is out, could you test?

[milesj]

@SimenB Yup seemed to fix it locally, will close.

[github-actions]

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.
Please note this issue tracker is not a help forum. We recommend using StackOverflow or our discord channel for questions.