vitest will crash when using ffi-napi

[LizardLiang]

Describe the bug

when using ffi-napi module, vitest cannot fully finish its job

after i remove file include ffi-napi, it becomes normal again

Reproduction

In any testing file add
const ffi = require('ffi-napi')

System Info

System:
    OS: Windows 10 10.0.19043
    CPU: (16) x64 Intel(R) Core(TM) i7-10700 CPU @ 2.90GHz
    Memory: 16.55 GB / 31.80 GB
  Binaries:
    Node: 16.17.0 - ~\scoop\apps\nvm\current\nodejs\nodejs\node.EXE
    npm: 8.15.0 - ~\scoop\apps\nvm\current\nodejs\nodejs\npm.CMD
  Browsers:
    Edge: Spartan (44.19041.1266.0), Chromium (105.0.1343.50)
    Internet Explorer: 11.0.19041.1566
  npmPackages:
    @vitejs/plugin-react: ^2.1.0 => 2.1.0
    vite: ^3.1.0 => 3.1.3
    vitest: ^0.23.4 => 0.23.4

Used Package Manager

npm

Validations

• Follow our Code of Conduct
• Read the Contributing Guidelines.
• Read the docs.
• Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
• Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
• The provided reproduction is a minimal reproducible example of the bug.

[sheremet-va]

According to node-ffi-napi/node-ffi-napi#125 you cannot use it inside a worker thread. Vitest runs tests only inside worker threads.

[marcoroth]

Is there any workaround for this? Or do I have to ditch vitest when testing modules using ffi-napi? 🥲

[AriPerkkio]

Is there any workaround for this?

Use --no-threads. Or if you are using v1-beta releases, use --pool=forks.

[AriPerkkio]

Fixed by #3925 and #4172.

Vitest 1.0.0-beta has now --pool=forks which uses multiple node:child_process in parallel. The previous --no-threads was using a single node:child_process.

If the code you are testing is incompatible with node:worker_threads, switch to --pool=forks. If you run into same error with that pool, feel free to open new issue with minimal reproduction.

[marcoroth]

Awesome, thanks @AriPerkkio! Using --pool=forks works perfectly!