AI_Assistant/pcbjam
Watch
1
0
Fork
You've already forked pcbjam
 0
Code Issues Pull requests Projects Releases 4 Packages Wiki Activity Actions 2

fix(boot): echo wasm dispatch/timer diagnostics to the browser console

Browse source 
Module.print feeds only the in-page log panel; it echoes to the JS console
solely under ?trace=. That is right for ordinary wasm chatter and wrong for the
two diagnostics wxwidgets now emits: production crash reports reach us as SAVED
BROWSER CONSOLE DUMPS, so a diagnostic that never leaves the page is invisible
in the one artifact we actually receive — and the in-page buffer is capped at
800 lines, so a long load can evict it before anyone reads it.

Narrow by construction: only the "[wx-dispatch]" and "[wx-timer]" prefixes, both
rate-limited in C++ and silent on a healthy load, so this cannot become noise.

Verified by driving Module.print directly in a real browser: the two prefixes
reach console.log / console.warn and an ordinary line does not.

Also bumps wxwidgets for those diagnostics.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_0137pGo8W7asomGUTRMB7RzM
This commit is contained in:
Gergő Törcsvári 2026-07-31 12:35:42 +02:00
commit b127b582bc
No known key found for this signature in database
GPG key ID: 8E75F2CDE64E5322
2 changed files with 21 additions and 3 deletions
Download patch file Download diff file Expand all files Collapse all files

22
web/standalone/src/wasm/boot.ts
View file

@ -166,6 +166,24 @@ function loadScript(src: string): Promise<void> {
* the page is COEP `require-corp`). The `.wasm`/`images.tar.gz` fetches just
* need `ACAO` + `CORP` on the CDN. See docs/features/demo-deploy/0001-*.
*/
/**
* C++ diagnostics that must reach the BROWSER console, not just the in-page log.
*
* Module.print normally feeds only the in-page buffer (capped at 800 lines, and
* echoed to the console only under ?trace=). That is right for ordinary wasm
* chatter, but wrong for these: production crash reports reach us as saved
* browser-console dumps, so a diagnostic that never leaves the page is invisible
* in the one artifact we actually receive — and it can be evicted from the
* capped buffer by a long load before anyone reads it.
*
* Deliberately narrow. Both emitters are rate-limited in C++ and silent on a
* healthy load (see wxwidgets src/wasm/{evtloop,timer}.cpp), so this cannot
* become noise.
*/
function isWasmDiagnostic(line: string): boolean {
return line.startsWith("[wx-dispatch]") || line.startsWith("[wx-timer]");
}
function pthreadWorkerScript(
base: string,
bundle: Bundle,
@ -526,12 +544,12 @@ async function doBoot(opts: BootOptions): Promise<void> {
log(`[out] ${m}`);
// With ?trace=, also echo to the JS console (the in-page log buffer is
// capped at 800 lines and would truncate a full-set trace run).
if (traceMask) console.log(m);
if (traceMask || isWasmDiagnostic(m)) console.log(m);
},
printErr: (...args: unknown[]) => {
const m = args.join(" ");
log(`[err] ${m}`);
if (traceMask) console.warn(m);
if (traceMask || isWasmDiagnostic(m)) console.warn(m);
},
setStatus: (text: string) => {
if (text) onStatus(text);