illegal instruction cpu error #8073

Closed
opened 2026-02-16 18:09:05 -05:00 by yindo · 2 comments
Owner

Originally created by @SHOOP111 on GitHub (Jan 30, 2026).

Originally assigned to: @rekram1-node on GitHub.

Description

i updated to the latest version and i got errors. seems like my cpu does not support AVX and uhhh can you guys please degrade bun to fix this?

Plugins

No response

OpenCode version

No response

Steps to reproduce

No response

Screenshot and/or share link

No response

Operating System

Windows 10

Terminal

No response

Originally created by @SHOOP111 on GitHub (Jan 30, 2026). Originally assigned to: @rekram1-node on GitHub. ### Description i updated to the latest version and i got errors. seems like my cpu does not support AVX and uhhh can you guys please degrade bun to fix this? ### Plugins _No response_ ### OpenCode version _No response_ ### Steps to reproduce _No response_ ### Screenshot and/or share link _No response_ ### Operating System Windows 10 ### Terminal _No response_
yindo added the windowsbugperf labels 2026-02-16 18:09:05 -05:00
yindo closed this issue 2026-02-16 18:09:05 -05:00
Author
Owner

@github-actions[bot] commented on GitHub (Jan 30, 2026):

This issue might be a duplicate of existing issues. Please check:

  • #8744: [Bug] Windows binary selection picks AVX version on non-AVX CPUs - This directly addresses the issue of OpenCode crashing on non-AVX CPUs with a detailed explanation and workaround
  • #8345: zsh: illegal hardware instruction opencode - Similar illegal instruction error on older Mac hardware without AVX support
  • #8611: v1.1.21-baseline crashing with Illegal Instruction (regression from v1.1.20) - Baseline binary still crashing on non-AVX CPUs
  • #641: Illegal instruction in linux - Related illegal instruction error on Linux

Feel free to ignore if your specific case is different from these issues, but #8744 in particular provides a detailed explanation of the root cause and potential workarounds for Windows users without AVX support.

@github-actions[bot] commented on GitHub (Jan 30, 2026): This issue might be a duplicate of existing issues. Please check: - #8744: [Bug] Windows binary selection picks AVX version on non-AVX CPUs - This directly addresses the issue of OpenCode crashing on non-AVX CPUs with a detailed explanation and workaround - #8345: zsh: illegal hardware instruction opencode - Similar illegal instruction error on older Mac hardware without AVX support - #8611: v1.1.21-baseline crashing with Illegal Instruction (regression from v1.1.20) - Baseline binary still crashing on non-AVX CPUs - #641: Illegal instruction in linux - Related illegal instruction error on Linux Feel free to ignore if your specific case is different from these issues, but #8744 in particular provides a detailed explanation of the root cause and potential workarounds for Windows users without AVX support.
Author
Owner

@Destreyf commented on GitHub (Jan 30, 2026):

@SHOOP111 if you're using the TUI version (which i'm guessing you are based on your bun comment), you can grab the baseline binary from the releases: opencode-windows-x64-baseline.zip

This should run on non avx cpu's, if you're using the desktop app, it doesn't look like they have a baseline build, and i'm not certain they can make one.

@Destreyf commented on GitHub (Jan 30, 2026): @SHOOP111 if you're using the TUI version (which i'm guessing you are based on your bun comment), you can grab the baseline binary from the releases: [opencode-windows-x64-baseline.zip](https://github.com/anomalyco/opencode/releases/download/v1.1.46/opencode-windows-x64-baseline.zip) This should run on non avx cpu's, if you're using the desktop app, it doesn't look like they have a baseline build, and i'm not certain they can make one.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: anomalyco/opencode#8073