[Bug]: Panic occurred when using Persistent Cache on Docusaurus

[slorber]

System Info

Rspack 1.2.3

System:
OS: macOS 15.2
CPU: (12) arm64 Apple M3 Pro
Memory: 4.80 GB / 36.00 GB
Shell: 5.9 - /bin/zsh
Binaries:
Node: 22.3.0 - ~/Library/Caches/fnm_multishells/70713_1737970350057/bin/node
Yarn: 1.22.22 - ~/Library/Caches/fnm_multishells/70713_1737970350057/bin/yarn
npm: 10.8.1 - ~/Library/Caches/fnm_multishells/70713_1737970350057/bin/npm
pnpm: 9.4.0 - ~/Library/pnpm/pnpm
bun: 1.1.45 - ~/.bun/bin/bun
Browsers:
Chrome: 133.0.6943.54
Chrome Canary: 135.0.7014.0
Safari: 18.2

Details

When using Persistent Cache on Docusaurus, I got this error after a while:

[PERF] Build > en > Load site > Load plugins - 1.03 seconds! - (67mb -> 120mb)
[PERF] Build > en > Load site > Create site files - 22.84 ms - (120mb -> 133mb)
[PERF] Build > en > Load site - 1.07 seconds! - (67mb -> 133mb)
[PERF] Build > en > Creating rspack bundler configs - 86.51 ms - (134mb -> 126mb)
● Client ██████████████████████████████████████████████████ (70%) sealing finish modules                                                                                                                           
● Server ██████████████████████████████████████████████████ (61%) building /Users/sebastienlorber/Desktop/projects/docusaurus/packages/docusaurus-mdx-loader/lib/index.js??ruleSet[1].rules[12].use[0]!/Users/sebasPanic occurred at runtime. Please file an issue on GitHub with the backtrace below: https://github.com/web-infra-dev/rspack/issues
Message:  should have module
Location: crates/rspack_plugin_javascript/src/plugin/infer_async_modules_plugin.rs:49

● Client ██████████████████████████████████████████████████ (70%) sealing finish modules                                                                                                                           
● Server ██████████████████████████████████████████████████ (70%) sealing finish modules                                                                                                                           ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ BACKTRACE ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
 1: _napi_register_module_v1
    at <unknown source file>
 2: _napi_register_module_v1
    at <unknown source file>
 3: _napi_register_module_v1
    at <unknown source file>
 4: _napi_register_module_v1
    at <unknown source file>
 5: _wasmer_vm_f64_nearest
    at <unknown source file>
 6: _wasmer_vm_f64_nearest
    at <unknown source file>
 7: _napi_register_module_v1
    at <unknown source file>
 8: _napi_register_module_v1
    at <unknown source file>
 9: _napi_register_module_v1
    at <unknown source file>
10: _napi_register_module_v1
    at <unknown source file>
11: _napi_register_module_v1
    at <unknown source file>
12: _napi_register_module_v1
    at <unknown source file>
13: _napi_register_module_v1
    at <unknown source file>
14: __pthread_deallocate
    at <unknown source file>
Panic occurred at runtime. Please file an issue on GitHub with the backtrace below: https://github.com/web-infra-dev/rspack/issues
Message:  should have module
Location: crates/rspack_plugin_javascript/src/plugin/infer_async_modules_plugin.rs:49

Run with COLORBT_SHOW_HIDDEN=1 environment variable to disable frame filtering.
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ BACKTRACE ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
 1: _napi_register_module_v1
    at <unknown source file>
 2: _napi_register_module_v1
    at <unknown source file>
 3: _napi_register_module_v1
    at <unknown source file>
 4: _napi_register_module_v1
    at <unknown source file>
 5: _wasmer_vm_f64_nearest
    at <unknown source file>
 6: _wasmer_vm_f64_nearest
    at <unknown source file>
error Command failed with signal "SIGABRT".
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
error Command failed.
Exit code: 1
Command: /Users/sebastienlorber/Library/Application Support/fnm/node-versions/v22.3.0/installation/bin/node
Arguments: /Users/sebastienlorber/Library/Application Support/fnm/node-versions/v22.3.0/installation/lib/node_modules/yarn/lib/cli.js build:fast
Directory: /Users/sebastienlorber/Desktop/projects/docusaurus/website
Output:

info Visit https://yarnpkg.com/en/docs/cli/workspace for documentation about this command.
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

Reproduce link

facebook/docusaurus#10931

Reproduce Steps

Repro PR / branch: facebook/docusaurus#10931

yarn install
yarn build:website:fast
yarn build:website:fast

The 2nd build fails. However it's not so easy to reproduce, and it seems to happen only in some cases 100% when trying to build our site in multiple flavors to check how the cache behaves.

For example:

yarn install

yarn build:website --locale en --locale fr
yarn build:website --locale en
yarn build:website:fast
yarn build:website --locale en
yarn build:website --locale fr
yarn build:website --locale fr
yarn build:website --locale en --locale fr
yarn build:website:fast

When alternating different build flavors, we end up with surprising results, one of them being the Rust error above that I thought you'd be interested to know. I'm not really able to reproduce it with clear steps, and hope you'll still find this report useful.

---

There are other non-Rust errors though, but they are probably my fault because changing the build flavors (using env variables) will alter the configuration of our MDX loaders, leading to different loader results.

We use this persistent cache version ${"client" | "server"}-${"prod" | "dev"}-${"en" | "fr}-${DOCUSAURUS_VERSION}

Edit: I was able to reproduce these errors with Webpack too. I guess if we use env variables this way, they should be added to the cache version.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. If this issue is still affecting you, please leave any comment (for example, "bump"). We are sorry that we haven't been able to prioritize it yet. If you have any new additional information, please include it with your comment!

[slorber]

I haven't reproduced it recently so it may be fixed already