swc's been segfaulting for me since morning. I was running a few months old project after updating it's dependencies; there are no errors in the code and I've no idea what's causing it.

Using the canary build also fails but with a different error (I'm putting both logs down). Thanks in advance!

Operating System:
  Platform: darwin
  Arch: arm64
  Version: Darwin Kernel Version 23.2.0: Wed Nov 15 21:55:06 PST 2023; root:xnu-10002.61.3~2/RELEASE_ARM64_T6020
Binaries:
  Node: 21.6.2
  npm: 10.2.4
  Yarn: 4.0.2
  pnpm: 8.14.0
Relevant Packages:
  next: 14.1.0
  eslint-config-next: 14.1.0
  react: 18.2.0
  react-dom: 18.2.0
  typescript: 5.2.2
Next.js Config:
  output: N/A

next build logs with next@14.1.0:

 ✓ Linting and checking validity of types
   Creating an optimized production build ...
thread '<unnamed>' panicked at /Users/geist/.cargo/registry/src/index.crates.io-6f17d22bba15001f/rkyv-0.7.42/src/rel_ptr/mod.rs:383:76:
called `Result::unwrap()` on an `Err` value: IsizeOverflow
stack backtrace:
Compiler server unexpectedly exited with code: null and signal: SIGSEGV

logs with next@^14.1.1-canary.59:

thread '<unnamed>' panicked at /Users/geist/.cargo/registry/src/index.crates.io-6f17d22bba15001f/wasmer-wasix-0.18.0/src/runtime/task_manager/tokio.rs:105:19:
there is no reactor running, must be called from the context of a Tokio 1.x runtime
stack backtrace:
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.
thread '<unnamed>' panicked at /Users/geist/.cargo/registry/src/index.crates.io-6f17d22bba15001f/wasmer-wasix-0.18.0/src/runtime/task_manager/tokio.rs:105:19:
there is no reactor running, must be called from the context of a Tokio 1.x runtime
...