Skip to content

YC (S26) | Open Computer History | Continuously record your company computer work, map your workflows, help you find work worth automating, and power your agents' context

ci(windows): SDE probes must emulate a PRE-AVX cpu (-wsm), not Sandy Bridge

Louis Beaumontf070b9a8a9f3
diff --git a/.github/workflows/release-cli.yml b/.github/workflows/release-cli.yml
index 53b8a1a09..bfa4b438a 100644
--- a/.github/workflows/release-cli.yml
+++ b/.github/workflows/release-cli.yml
@@ -594,17 +594,18 @@ jobs:
path: screenpipe-*.zip
# Non-AVX2 launch + ONNX-init smoke against the exact deployment package,
- # under Intel SDE -snb (Sandy Bridge: AVX but NO AVX2 — the pre-Haswell /
- # Atom-line customer class from #3125). CI runners have AVX2, so without
- # SDE an AVX2-poisoned build sails through CI and dies with 0xC000001D on
- # customer machines — this job is the permanent regression guard, and
- # `release`/`publish-npm` require it.
+ # under Intel SDE -wsm (Westmere: SSE4.2, NO AVX, no AVX2 — the customer
+ # CPU class from #3125: Celeron N5095 / Jasper Lake has no AVX, and the
+ # original report's QEMU `-cpu qemu64` is baseline SSE2). CI runners have
+ # AVX2, so without SDE an AVX-poisoned build sails through CI and dies with
+ # 0xC000001D on customer machines — this job is the permanent regression
+ # guard, and `release`/`publish-npm` require it.
#
# Separate job from build-windows on purpose: SDE's Pin injector is broken
# on windows-2022 runners ("Invalid file name and base dir combination:
# pincrt4.dll" — runs 28806190901 and 30653241813, both SDE 10.8 kits).
# windows-latest (Server 2025) is the image google/XNNPACK runs the same
- # kit + -snb probes on. The build stays on windows-2022 for toolchain
+ # kit + SDE probes on. The build stays on windows-2022 for toolchain
# stability; this job only downloads and runs its artifacts.
smoke-windows:
name: Non-AVX2 smoke (Intel SDE)
@@ -632,13 +633,28 @@ jobs:
# ("Injection failed with code ffffffff" — 10.8 on windows-2022 +
# windows-latest regardless of extraction/invocation, lab run
# 30658575297; 10.5 + 10.7 likewise, lab run 30659124066). 9.58
- # launched this exact package green under -snb in the same lab
+ # launched this exact package green under SDE in the same lab
# run. 10.8 DOES work on real Windows 11 — for local repro any
# recent kit is fine.
- # - -snb ONLY. Pre-AVX chips (-nhm/-mrm) are a false-negative trap:
- # modern hosts' system DLLs execute AVX, so emulating pre-AVX
- # faults in the OS, not our code. The no-AVX floor is covered by
- # baseline codegen + the runtime AVX2 gates.
+ # - -wsm (Westmere: SSE4.2, NO AVX, no AVX2), NOT -snb. This is the
+ # single most important knob here and it was wrong before.
+ # Sandy Bridge HAS AVX, and /arch:AVX2 codegen emits VEX-encoded
+ # AVX instructions that run happily there — measured on a real
+ # Windows guest: the pre-fix build ran `record` for 420s under
+ # SandyBridge but died in 1.4s under Westmere with
+ # "Exception code: 0xc000001d" in the Application event log,
+ # faulting module screenpipe.exe. The affected customer CPUs have
+ # no AVX at all (Celeron N5095 = Jasper Lake/Tremont; the original
+ # report's QEMU `-cpu qemu64` is baseline SSE2), so an -snb probe
+ # passes builds that crash in the field. Verified both ways with
+ # the packaged exes: under -wsm the pre-fix build faults on
+ # `vpxor xmm0, xmm0, xmm0` inside screenpipe.exe, the fixed build
+ # prints its version. AVX2 ⊂ AVX, so -wsm covers the AVX2 case too.
+ # - -chip_check_exe_only makes pre-AVX emulation usable: it scopes the
+ # chip check to the main image, so the host's own system DLLs (which
+ # execute AVX regardless of the emulated chip) can't produce false
+ # failures. That trap is why the original probe avoided pre-AVX
+ # targets; the flag removes it. Negative controls still fire.
# - -chip_check_exe_only (same conclusion google/XNNPACK reached):
# MS runtime DLLs (VCRUNTIME140 etc.) dispatch via OS feature
# checks SDE cannot spoof, so on an AVX-512 HOST the bundled
@@ -652,7 +668,7 @@ jobs:
# CPUID for every DLL (onnxruntime's MLAS keys off in-process
# CPUID, which SDE does spoof). Negative control re-verified WITH
# the flag: stock AVX2 bun.exe still faults (vinserti128, main
- # image) under -snb -chip_check_exe_only.
+ # image) under -wsm -chip_check_exe_only.
# - Hard timeout per invocation + job timeout: a wedged emulator must
# fail fast and loud, never eat runner-hours.
# - Intel rotates mirrors (9.44.0's died 2026-07-31, run 30651369680).
@@ -689,17 +705,17 @@ jobs:
# Probe 1: the packaged CLI launches without AVX2 — catches the
# 0xC000001D static-init crash class (global /arch:AVX2 CFLAGS,
# AVX2 static onnxruntime, eager ggml init...).
- Write-Host "=== SDE -snb — screenpipe.exe --version (8 min timeout; ~2s native) ==="
- $p = Start-Process -FilePath $sde -ArgumentList @('-snb','-chip_check_exe_only','--',$exe,'--version') `
+ Write-Host "=== SDE -wsm — screenpipe.exe --version (8 min timeout; ~2s native) ==="
+ $p = Start-Process -FilePath $sde -ArgumentList @('-wsm','-chip_check_exe_only','--',$exe,'--version') `
-NoNewWindow -PassThru -RedirectStandardOutput sde-out.txt -RedirectStandardError sde-err.txt
if (-not $p.WaitForExit(480000)) {
taskkill /PID $($p.Id) /T /F | Out-Null
Get-Content sde-out.txt, sde-err.txt -ErrorAction SilentlyContinue
- throw "SDE -snb launch probe timed out after 8 minutes — emulator wedged or a startup-path hang on non-AVX2 CPUs"
+ throw "SDE -wsm launch probe timed out after 8 minutes — emulator wedged or a startup-path hang on pre-AVX CPUs"
}
Get-Content sde-out.txt, sde-err.txt -ErrorAction SilentlyContinue
- if ($p.ExitCode -ne 0) { throw "screenpipe.exe faulted under SDE -snb (exit $($p.ExitCode)) — a non-AVX2 CPU cannot launch this build" }
- Write-Host "=== SDE -snb launch probe passed ==="
+ if ($p.ExitCode -ne 0) { throw "screenpipe.exe faulted under SDE -wsm (exit $($p.ExitCode)) — a pre-AVX/non-AVX2 CPU cannot launch this build" }
+ Write-Host "=== SDE -wsm launch probe passed ==="
# Probe 2: ONNX Runtime (the shipped MS DirectML DLL) actually
# INITIALIZES without AVX2 — MLAS runtime CPUID dispatch must pick
@@ -707,18 +723,18 @@ jobs:
# created on the audio boot path), so this is the probe that
# directly covers the pyke-AVX2-static-lib crash class for
# VAD/diarization/PII.
- Write-Host "=== SDE -snb — ort-smoke (8 min timeout; probe deadline 420s) ==="
+ Write-Host "=== SDE -wsm — ort-smoke (8 min timeout; probe deadline 420s) ==="
$env:ORT_SMOKE_DEADLINE_SECS = "420"
- $p2 = Start-Process -FilePath $sde -ArgumentList @('-snb','-chip_check_exe_only','--',(Resolve-Path "smoke-probes/ort-smoke.exe").Path) `
+ $p2 = Start-Process -FilePath $sde -ArgumentList @('-wsm','-chip_check_exe_only','--',(Resolve-Path "smoke-probes/ort-smoke.exe").Path) `
-NoNewWindow -PassThru -RedirectStandardOutput ort-sde-out.txt -RedirectStandardError ort-sde-err.txt
if (-not $p2.WaitForExit(480000)) {
taskkill /PID $($p2.Id) /T /F | Out-Null
Get-Content ort-sde-out.txt, ort-sde-err.txt -ErrorAction SilentlyContinue
- throw "ort-smoke timed out under SDE -snb after 8 minutes — emulator wedged or ONNX init hangs on non-AVX2 CPUs"
+ throw "ort-smoke timed out under SDE -wsm after 8 minutes — emulator wedged or ONNX init hangs on non-AVX2 CPUs"
}
Get-Content ort-sde-out.txt, ort-sde-err.txt -ErrorAction SilentlyContinue
- if ($p2.ExitCode -ne 0) { throw "ONNX Runtime failed to initialize under SDE -snb (exit $($p2.ExitCode)) — the shipped DLL cannot init on non-AVX2 CPUs" }
- Write-Host "=== SDE -snb ort probe passed: ONNX Runtime initializes without AVX2 ==="
+ if ($p2.ExitCode -ne 0) { throw "ONNX Runtime failed to initialize under SDE -wsm (exit $($p2.ExitCode)) — the shipped DLL cannot init on pre-AVX CPUs" }
+ Write-Host "=== SDE -wsm ort probe passed: ONNX Runtime initializes without AVX ==="
build-linux:
needs: check_commit
diff --git a/TESTING.md b/TESTING.md
index 3770c7d26..a6c38e10e 100644
--- a/TESTING.md
+++ b/TESTING.md
@@ -484,7 +484,7 @@ commits: `b3628788`, `738178da`
commits: `eea0c865`, `fe9060db`, `c99c3967`, `aeaa446b`, `5a219688`, `caae1ebc`, `67caf1d1`, `ff4af7b5`
-- [ ] **non-AVX2 CPU launch (compatibility mode)** — (#3125) On x86-64 CPUs without AVX2 (pre-2013 Intel, Atom-line Celeron/Pentium, QEMU `-cpu qemu64`), the app and CLI must LAUNCH and RECORD instead of dying with `0xC000001D STATUS_ILLEGAL_INSTRUCTION`. Local whisper/qwen3 STT is disabled at runtime (AVX2-compiled kernels); parakeet + cloud engines keep working; onboarding shows a "compatibility mode" notice. Guards: never set global `CFLAGS/CXXFLAGS=/arch:AVX2` in Windows release workflows (it poisons every cc/cmake dep incl. bundled SQLite → crash in static initializers before main); ONNX Runtime must stay on the MS DirectML DLL (import-table link, runtime CPUID dispatch) — pyke's `download-binaries` static libs are AVX2-only. CI: `release-cli.yml`'s `smoke-windows` job (runs-on windows-latest — SDE's Pin injector is broken on windows-2022) runs the packaged exe AND an ONNX-init probe (`.github/ci/ort-smoke`, real `Session::builder()` against the shipped DirectML DLL) under Intel SDE `-snb` (Sandy Bridge, no AVX2) on every Windows CLI build, and `release`/`publish-npm` require it; `release-app.yml` probes the app exe natively via the hidden `--cpu-smoke` flag (static init + import table). Reproduce locally with `sde -snb -- screenpipe.exe --version`, or QEMU `-cpu qemu64` for the app. Pipes/AI chat on such CPUs use bun's official `windows-x64-baseline` build (runtime-downloaded, mandatory SHA-256; verified 2026-07-31 to run under `sde -snb` while stock bun faults).
+- [ ] **pre-AVX / non-AVX2 CPU launch (compatibility mode)** — (#3125) On x86-64 CPUs without AVX (Atom-line Celeron/Pentium such as the N5095 = Jasper Lake/Tremont, pre-2011 Intel, QEMU `-cpu qemu64`), the app and CLI must LAUNCH and RECORD instead of dying with `0xC000001D STATUS_ILLEGAL_INSTRUCTION`. **Test on a NO-AVX CPU, not merely a no-AVX2 one**: measured on real Windows guests, the pre-fix build ran `record` for 420s under an emulated Sandy Bridge (which has AVX) and died in 1.4s under Westmere (no AVX) with `Exception code: 0xc000001d`, faulting module `screenpipe.exe`. `/arch:AVX2` codegen emits VEX-encoded AVX instructions, so a Sandy-Bridge-class probe passes builds that crash in the field. Local whisper/qwen3 STT is disabled at runtime (AVX2-compiled kernels); parakeet + cloud engines keep working; onboarding shows a "compatibility mode" notice. Guards: never set global `CFLAGS/CXXFLAGS=/arch:AVX2` in Windows release workflows (it poisons every cc/cmake dep incl. bundled SQLite → crash in static initializers before main); ONNX Runtime must stay on the MS DirectML DLL (import-table link, runtime CPUID dispatch) — pyke's `download-binaries` static libs are AVX2-only. CI: `release-cli.yml`'s `smoke-windows` job (runs-on windows-latest — SDE's Pin injector is broken on windows-2022, and every SDE 10.x kit fails injection on current hosted images; 9.58 works) runs the packaged exe AND an ONNX-init probe (`.github/ci/ort-smoke`, real `Session::builder()` against the shipped DirectML DLL) under Intel SDE `-wsm -chip_check_exe_only` on every Windows CLI build, and `release`/`publish-npm` require it; `release-app.yml` probes the app exe natively via the hidden `--cpu-smoke` flag (static init + import table). `-chip_check_exe_only` is what makes pre-AVX emulation usable — it scopes the chip check to the main image so the host's own AVX-executing system DLLs can't cause false failures. Reproduce locally with `sde -wsm -chip_check_exe_only -- screenpipe.exe --version` (pre-fix build faults on `vpxor`; fixed build prints its version), or QEMU `-cpu Westmere`/`-cpu qemu64` for a full guest. Pipes/AI chat on such CPUs use bun's official `windows-x64-baseline` build (runtime-downloaded, mandatory SHA-256; verified 2026-07-31 to run under `sde -snb` while stock bun faults).
- [ ] **COM thread conflict** — audio and vision threads don't conflict on COM initialization (`eea0c865`).
- [ ] **high-DPI display (150%, 200%)** — OCR captures at correct resolution.
- [ ] **multiple monitors** — all detected and recorded.