| Filename | Latest commit message | Latest commit date |
|---|---|---|
54e6560037Converting the symbol-library bridge from one EM_ASYNC_JS into beginWait -> start -> wxWasmYieldUntil -> take_result made the app hang after every library request: the KiCad suite went from 7 minutes to 1.2 HOURS, 111 passed with the rest timing out, and the log goes silent right after a lib request - a parked context nobody resumes. Reverted; the tree keeps the working EM_ASYNC_JS and no code from the attempt. Recorded for the next attempt: - The PRECONDITION it found (four lines, quoted in the doc, deliberately NOT landed): wxWasmYieldUntil must not park a context whose wait is already resolved, because resolveWait deletes the entry. The in-place form had no such window; every bridge in this pattern re-opens it. It was not the hang, but it has only ever existed in the broken build, so it lands WITH the conversion it protects, not before. - Three hypotheses in evidence order, cheapest first: the resolve never reaching the registry (this is the first KiCad-side caller of the wait registry - check Module["_wxWasmSchedResolveContextWait"] exists in the KiCad link); the lib request running inside the chooser's modal where the dispatch context is ALREADY parked on a nested wait (a context holds one park); or the Asyncify instrumentation closure shifting when the EM_ASYNC_JS left that translation unit. - Process: gate a bridge conversion on a SINGLE spec, never the full suite. This cost a 1.2-hour run to learn one bit. Tree is unchanged from the last verified landing state (STAR_DISPATCH=0, kicad 139 passed / 1 pre-existing occ-probe) - docs only. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01LBjomQfKyRa3jBdeAKpmTw |
||
| .. | ||
| 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):