You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
v1.1.21-baseline crashing with Illegal Instruction (regression from v1.1.20) #8611
Hey, I'm getting an 'Illegal instruction' crash with the latest v1.1.21 baseline build on my older laptop.
Everything was working fine on v1.1.20, but after updating to v1.1.21 it started crashing immediately. It looks like a Bun panic related to missing AVX support, even though I'm using the baseline build which is supposed to support older CPUs.
Here is the panic log:
CPU lacks AVX support. Please consider upgrading to a newer CPU.
panic(main thread): Illegal instruction at address 0x4001FB4
oh no: Bun has crashed. This indicates a bug in Bun, not your code.
My specs:
CPU: Intel Pentium B980 (No AVX support)
OS: Ubuntu 24.04.3 LTS
Kernel: 6.14.0
I've downgraded back to v1.1.20 for now and it's working again, so it definitely seems like a regression in the new version. Any chance this can be looked into for the next update?
All of these appear to be related to the baseline build's CPU compatibility handling. Feel free to ignore if your specific case differs from these issues.
Just to clarify, this isn't a duplicate of those older issues. I've tested this specifically and verified that v1.1.20-baseline works perfectly on this same machine, while v1.1.21-baseline crashes.
This seems to be a new regression in the latest release's baseline build.
Even after downgrading (aur) to 1.1.18 bum crash issue, whether plugins like Pty and oh-my-opencode are configured or not. Edit: executable installed via official installer was still configured in shells, durp. Editing package.json and installing 1.1.20 binary in $HOME/.config/opencode/bin only launches successfully one time. Will report back.
Edit: mv executable, make a shell script to execute the binary with OPENCODE_NO_AUTO_UPDATE=1 ./opencode-binary
or just remember the var, or opencode.json(c) "autoupdate": true,
Activity
github-actions commentedon Jan 15, 2026
This issue might be a duplicate of existing issues. Please check:
All of these appear to be related to the baseline build's CPU compatibility handling. Feel free to ignore if your specific case differs from these issues.
dani931004 commentedon Jan 15, 2026
Just to clarify, this isn't a duplicate of those older issues. I've tested this specifically and verified that v1.1.20-baseline works perfectly on this same machine, while v1.1.21-baseline crashes.
This seems to be a new regression in the latest release's baseline build.
pushad commentedon Jan 15, 2026
I can also confirm this is affecting me since v1.1.21. When reverting to v1.1.20, opencode does not crash on boot.
Diphia commentedon Jan 15, 2026
also been seeing this since v1.1.21, and the address 0x4001FB4 is always the same
Nsomnia commentedon Jan 15, 2026
Even after downgrading (aur) to 1.1.18 bum crash issue, whether plugins like Pty and oh-my-opencode are configured or not. Edit: executable installed via official installer was still configured in shells, durp. Editing package.json and installing 1.1.20 binary in $HOME/.config/opencode/bin only launches successfully one time. Will report back.
Edit: mv executable, make a shell script to execute the binary with OPENCODE_NO_AUTO_UPDATE=1 ./opencode-binary
or just remember the var, or opencode.json(c) "autoupdate": true,
joao-coli commentedon Jan 15, 2026
Same thing, only on v1.1.21 when running on my older (i7 first-gen) machine.
binaryfire commentedon Jan 15, 2026
Same problem. Crash followed by random chars in the terminal.
rekram1-node commentedon Jan 15, 2026
Bun bug :/
rekram1-node commentedon Jan 15, 2026
We will just downgrade bun, that should fix it in next release
rekram1-node commentedon Jan 15, 2026
Should be fixed by: 5a8a0f6
Will release later today