[Bug]: Panic on arm64 with `performance.buildCache = true`

[regisb]

System Info

  OS: Linux 5.15 Debian GNU/Linux 11 (bullseye) 11 (bullseye)
  CPU: (4) arm64 Neoverse-N1
  Memory: 13.17 GB / 15.15 GB
  Container: Yes
  Shell: 5.1.4 - /bin/bash
Binaries:
  Node: 20.18.0 - /usr/local/bin/node
  Yarn: 1.22.22 - /usr/local/bin/yarn
  npm: 10.8.2 - /usr/local/bin/npm

Details

I am attempting to build an application in Docker, both on arm64 and amd64. The build is successful on amd64, but fails on arm64. Build is successful on arm64 when I disable caching.

Here's the error message (or rather, the lack thereof):

1.047 info    Rspack persistent cache enabled (experimental)
4.211 Panic occurred at runtime. Please file an issue on GitHub with the backtrace below: https://github.com/web-infra-dev/rspack/issues
4.211 Message:  created a new `Panic` from: out of range integral type conversion attempted
4.212 Location: index.crates.io-1949cf8c6b5b557f/rancor-0.1.0/src/lib.rs:648
4.214
4.214 Run with COLORBT_SHOW_HIDDEN=1 environment variable to disable frame filtering.
4.215 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ BACKTRACE ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
4.228  1: start_thread
4.228     at <unknown source file>
4.362 Aborted (core dumped)

This issue is consistently reproduced on an Apple M1 or M2. I do not own an Apple computer, but I was able to reproduce the issue by building on a remote arm64 server.

This issue was first reported here: overhangio/tutor-mfe#252 (comment)

Reproduce link

https://github.com/regisb/rsbuild-arm64-failure

Reproduce Steps

git clone https://github.com/regisb/rsbuild-arm64-failure .
make build-arm64-with-cache

Note that the following commands complete successfuly:

make build-arm64-no-cache
make build-amd64-with-cache

[1714080902120]

I'm running into this issue as well. I ran into another bug before that, which I ran into after removing ts-checker. It failed in linux arm64, but work well in window arm64. 1.3.5,1.3.4,1.3.3 are all build fail, but falling back to 1.3.2 builds fine

[chenjiahan]

@jerrykingxyz cc

[jerrykingxyz]

This issue seems to be caused by some unstable code. I have reproduced it and tried to fix it.