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
fix(win): EMCC_CORES=128 causes emcc subprocess crashes during system-lib build #116
After fixes #111, #113, #114, #115, the build proceeds through library compile, sketch compile, and starts the final em++ wasm link. While emscripten builds its sysroot libraries from source, an emcc subprocess crashes with an access-violation-style exit code:
crates/fastled-cli/src/wasm_build.rs unconditionally sets EMCC_CORES=128 on Windows. That tells emscripten to spawn up to 128 concurrent emcc Python subprocesses during the libc/compiler_rt build. On typical hardware that vastly exceeds the host's logical-core count, and Windows process pressure plus Python's slow startup makes one of them flake (exit code 3221356611, which is in the access-violation family).
Fix
Replace the hard-coded 128 with std::thread::available_parallelism() clamped to ~32. Match the host.
Resolved by merged PR #118 (e008ca3e). Current origin/main sets EMCC_CORES from std::thread::available_parallelism().min(32) instead of hard-coding 128, avoiding excessive Windows emcc subprocess fan-out.
Activity
zackees commentedon Jun 2, 2026
Resolved by merged PR #118 (
e008ca3e). Currentorigin/mainsetsEMCC_CORESfromstd::thread::available_parallelism().min(32)instead of hard-coding 128, avoiding excessive Windows emcc subprocess fan-out.