Illegal instruction error - Raspberry PI 4 aarch64

[adasek]

Hi, recently unrs-resolver got into my Nuxt3 stack that I'm running via Gitlab CI on Raspberry PI 4. Some steps in my pipeline began to emit Illegal instruction error. I traced the problem to unrs-resolver.

Minimal example

I created a minimal example that uses current v1.5.0 of unrs-resolver

Expected output:

Resolved: {
  path: 'node_modules/unrs-resolver/index.js',
  packageJsonPath: 'node_modules/unrs-resolver/package.json'
}

Output on Raspberry Pi 4 (aarch64)

Illegal instruction

System info

I tested on two Raspberry Pi 4 systems:

Linux raspberrypi 6.1.21-v8+ #1642 SMP PREEMPT Mon Apr  3 17:24:16 BST 2023 aarch64 GNU/Linux

and a clean installation of Raspberry Pi OS (64-bit), fully updated

Linux rpi4 6.12.20+rpt-rpi-v8 #1 SMP PREEMPT Debian 1:6.12.20-1+rpt1~bpo12+1 (2025-03-19) aarch64 GNU/Linux

both with node version v22.14.0

Rpi4 Features in /proc/cpuinfo:
Features : fp asimd evtstrm crc32 cpuid

The code runs without error on Raspberry Pi 5

Let me know if you need any additional info.

[JounQin]

In the meantime, you can use NAPI_RS_FORCE_WASI=true and install @unrs/resolver-binding-wasm32-wasi manually.

[JounQin]

@adasek Could help to confirm whether v1.6.1 works on Raspberry PI 4 aarch64?

[adasek]

Hi @JounQin, it's working 🎉

The v1.6.1 version flawlessly runs on Rpi4 aarch64 in both my minimal example and in my Nuxt3 web build+lint stack.

Thank you for the quick fix!

[JounQin]

@adasek Also thanks for debugging and helping us finding the root cause!

[JounQin]

@adasek Would you like to try out the latest https://github.com/unrs/unrs-resolver/releases/tag/v1.7.0 which enables mimalloc-safe on linux-aarch64 again with #98, I need to confirm if it's working as expected. ❤️

[adasek]

Hi @JounQin
unrs-resolver broke down again between 1.6.6 -> 1.7.0 on my Rpi4 aarch64

The minimal example on my system:

• 1.6.6 -> works
• 1.7.0 -> exit code 132 with Illegal instruction
• 1.7.8 -> exit code 132 with Illegal instruction

The stack trace i get in lldb node with current unrs-resolver master is:

(lldb) run ./src/index.js
Process 73115 launched: '/usr/bin/node' (aarch64)
Process 73115 stopped
* thread #1, name = 'node', stop reason = signal SIGILL: illegal instruction
    frame #0: 0x0000007ff42eaa30 resolver.linux-arm64-gnu.node`mi_process_init at atomic.h:343:10
   340 	static inline bool mi_atomic_once( mi_atomic_once_t* once ) {
   341 	  if (mi_atomic_load_relaxed(once) != 0) return false;     // quick test
   342 	  uintptr_t expected = 0;
-> 343 	  return mi_atomic_cas_strong_acq_rel(once, &expected, (uintptr_t)1); // try to set to 1
   344 	}
   345 	
   346 	typedef _Atomic(uintptr_t) mi_atomic_guard_t;