SIGILL leads to openclaw crash on AVX-only CPU

[zhanghe9704]

Plugin Version

v1.1.0-beta.10

OpenClaw Version

2026.4.15

Bug Description

I'm running OpenClaw in an old laptop with i7 3rd gen CPU, which supports AVX but not AVX2. After installing and enabling this plugin, OpenCLaw kept crashing every ~60 seconds due to SIGILL. It runs stable after disable the plugin.

I asked OpenClaw to reinstall the plugin from github repo, recompile LanceDB without AVX2 flags and replace the original LanceDB with the locally compiled one, but the SIGILL persists.

Expected Behavior

The readme says "CPU Requirement: Your CPU must support AVX/AVX2 instructions (Intel Sandy Bridge 2011+ / AMD Bulldozer 2011+). LanceDB's native vector engine requires these — on unsupported CPUs the plugin will crash with SIGILL (Illegal Instruction). Check with: grep -o 'avx[^ ]*' /proc/cpuinfo | head -1 (no output = not supported). See #419 for details."

So I expect AVX-only CPU will work. Can this be fixed? Or is AVX2 required?

Steps to Reproduce

Run OpenClaw in i7 3rd gen CPU. Install the plugin and enable it. OpenClaw keeps crashing and restarting.

Error Logs / Screenshots

Embedding Provider

None

OS / Platform

No response

[AliceLJY]

Thanks for the clear report. If the current docs imply AVX-only CPUs are supported but the plugin still crashes with SIGILL, then either the documented requirement is too loose or some native dependency path is still effectively AVX2-only. Either way, that is a real bug/docs mismatch worth tracking.

If you can attach the crash stack or identify which native binary is faulting, that would help narrow whether this is LanceDB packaging, binary selection, or another transitive native dependency.

[zhanghe9704]

downgraded to v1.1.0-beta.6, the SIGILL is gone. Up to beta.7, the SIGILL is back.

I asked my agent to look into it. The following is the report: (I can't confirm whether it's correct or not.)

Here's the definitive answer from the kernel log:

traps: tokio-runtime-w[522551] trap invalid opcode ip:7e241d583728 sp:7e24189fdeb8 error:0
in lancedb.linux-x64-gnu.node[7e2418e0c000+5dd4000]
Faulting binary: lancedb.linux-x64-gnu.node — confirmed, it's LanceDB's native Rust binary.
Faulting thread: tokio-runtime-w — LanceDB's Rust tokio async runtime worker
Fault type: trap invalid opcode (SIGILL) at offset 0x4777728 inside the .node binary
Error code: 0 (not a page fault — CPU literally couldn't decode the instruction)

Key detail: The crash happens on a tokio runtime worker thread inside LanceDB's native code, not on the Node.js main thread. This means:

• It's not V8 JIT — confirmed by --no-opt not helping
• It's not Node.js itself

• It's specifically LanceDB's Rust code executing an instruction that Ivy Bridge doesn't support (AVX2)
• The fault is deterministic — same IP address (0x7e241d583728) on multiple threads, meaning it's the same code path every time

Why beta.6 doesn't crash: Beta.6 doesn't call .distanceType('cosine') or trigger the heavier vector search patterns that activate the AVX2 code path in LanceDB's Rust runtime.