| Filename | Latest commit message | Latest commit date |
|---|---|---|
5a3dd44b23Bumps wxwidgets d220aae5 (D2a: sched_context.h moved into wx's port, header-only so evtloop.cpp can see it) and 5ee60a81 (D1 fix: 16-align context stacks — EM_ASM's arg buffer lives on the running stack and the glue asserts buf % 16 == 0, so misaligned contexts trapped in readEmAsmArgs; std::vector<char> only gives malloc's 8-byte alignment). The dispatch switch itself is NOT landed. Running the tick's ProcessEvents on a context took the battery from 363 green to 388/7, six of them the coroutine-nested harness wedging at fiber_create_run_destroy_inside_modal via aliased-wake-live -> fiber-resume-refused — doc 19's mechanism. A quasi-modal opened from a tick handler suspends the dispatch context INSIDE the still-in-place wait, putting one more Asyncify layer under every libcontext fiber. Pooling contexts (8 burned in 30 ms) and falling back to entry-stack dispatch both failed to avoid it, because the layer exists as soon as the context is suspended. That is doc 20's own risk 2 arriving on schedule, so the plan is corrected rather than the symptom patched: D3 (waits become context yields) must come first, after which the dispatch context is released at its tick boundary instead of suspended and the failure class is structurally absent. Verified the revert: the nested battery is green again at this baseline (5 passed / 1 failed, the 1 being the environment-sensitive modal:125 that also fails without any of this). Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01TEHGiiXMShNXbBr7gSJ7iz |
||
| .. | ||
| debugging | ||
| features | ||
| research | ||
| build.md | ||
| ci-build-slowness-findings.md | ||
| README.md | ||
| wasm-exceptions-experiment.md | ||
Documentation Map
A central index of the documentation in this repo. The goal of the project is to build KiCad with WASM and run it in a browser.
Note: per-area
README.mdfiles stay next to the code they describe (they're linked below). Cross-cutting guides live underdocs/. Per-feature design notes live underfeatures/.
Start here
- Project README — overview, prerequisites, quick start, project structure
- CLAUDE.md — project/agent context and contribution conventions
Build
- docs/build.md — Docker-based KiCad WASM build system (two-phase build, outputs, memory)
- docker/README.md — Docker build environment, branch-specific containers, troubleshooting
- wasm/README.md — WASM compatibility layer (overrides/shims without patching KiCad)
Debugging & Asyncify
- docs/debugging/DEBUG.md — debugging guide: Asyncify stalls vs crashes, shim/codegen coupling, stub-bisection
- docs/debugging/learning.md — Asyncify + consecutive modal dialogs: the lock pattern
- docs/research/threading_1.md — deep dive: the Asyncify single-slot
currDatacollision bug and the fix - docs/research/threading_2.md — external research: JSPI/WasmFX/state-machine alternatives, QEMU analysis
Architecture
- wasm/README.md — WASM compatibility layer structure
- web/README.md — web app (create/open KiCad projects), tech stack, URL routing, WASM artifact serving
Testing
- tests/README.md — Playwright test infrastructure, element registry, logs, screenshots
- tests/WHATWORKS.md — wxWidgets-in-WASM feature coverage matrix and KiCad readiness
- tests/GL_README.md — Emscripten legacy GL immediate-mode quirks (color-per-vertex)
- tests/gal-regression/README.md — GAL visual regression suite (native OpenGL vs WebGL WASM)
Feature design docs
Per-feature design notes and porting records live under features/:
- web-init — web app spec
- schematic — eeschema WASM bring-up
- symbol-editor — symbol editor (eeschema kiface launcher)
- gerbview — Gerber viewer port
- pl-editor — page-layout editor port (incl. file-dialog usability fixes)
- browser-tools — tool-activation / coroutine deep dives
- fix-asyncify-O2-and-modal-promise-rejection — RTree wasm overflow bug investigation
Archived / historical
features/archive/ holds docs whose work is done or superseded
(each carries a status banner):