Repository navigation
Conversation
2026-10-24 — low-risk synchronous ADB cache I/O reductionWhat changed on this DRAFT branch (latest commit
Real Windows validation (
Limitations: These are functional and source-I/O improvements, not a measured startup latency regression fix. Most cache work is still synchronous before the first window. No new slow-start trace has yet pinned the duration to this stage. Do not close issue #44 or merge this draft based on this optimization alone. Prior HDD crossover benchmark failed in preflight without valid app timing; it cannot supply evidence for this change. |
2026-10-24: gated A/B experiment and newly measured pre-window I/OTwo new trace-on, isolated-userData starts using the prior packaged QA binary showed an 11,060ms window on the first attempt vs 888ms on the second. ADB fingerprint took 4,095ms vs 28ms; native Added QA-ONLY, explicitly gated Commit |
QA checkpoint: packaged ABBA test deferred due unresponsive Windows packager (2026-10-24)Source change on However packaging did not complete:
No current ASAR verifier pass exists for this new commit, and no normal-vs-skip ADB-cache startup A/B has been run. The interrupted Logs at |
2026-10-24 — 8/8 isolated ADB-cache A/B starts; no production change proposed yetCompleted a counterbalanced ABBA sequence (first 2, brief safety-harness interruption, then last 2) and a reversed BAAB sequence on the same Windows HDD QA host. All eight trials achieved
Critical package qualifier: The standard electron-builder directory packaging repeatedly stalled on the HDD after Node/web typecheck and Vite main/preload/renderer builds. Rather than use incomplete dist, created a manually assembled QA-only executable in Interpretation: Skip mode was faster in this small, uncontrolled sample, but OS disk-cache/warm-up, mode order, and ADB path differences confound causation. Even the 21s outlier spent most time outside ADB fingerprinting. Do not remove production ADB integrity validation. A safer potential production design is making UI window/renderer readiness independent of synchronous ADB-runtime preparation, while gating all ADB-dependent IPC until runtime preparation completes; this needs dedicated tests and installed-NSIS QA before merge. Raw CSV summaries: |
CPU-heartbeat v7: packaged Windows validation completed (2026-10-24)Commit Eight isolated sequential normal-icon starts: 8/8 PASS, no leftovers, shown-window uptime in ms: 1117, 1034, 1035, 1114, 1047, 545, 1255, 552 (range 545–1255ms, conventional median 1041ms). All started too quickly to record a periodic CPU heartbeat. Initial local summary printed an incorrect 1047ms "median" by selecting the upper middle element; corrected the F: reporting script. To verify actual packaged CPU-field emission, used an isolated copy of the existing QA harness (not the repository harness), keeping one ready QA instance open six extra seconds. 1/1 PASS; zero leftover v7 processes. Trace: Evidence saved under |
#44 QA follow-up (2026-10-24): 12 more valid Windows starts; CPU-correlated trace reports verifiedSame frozen/manual v7 binary and normal icon, 12/12 sequential fresh-profile launches PASS (harness exit 0), 0 invalid JSONL records and 0 orphaned QA executables. Native window-shown process uptime: 1105, 1294, 1129, 1097, 1034, 1180, 946, 1096, 1058, 1089, 1084, 1093ms (min 946ms, conventional median 1094.5ms, max 1294ms). This is another fast series, not a reproduction of the historical 18.284s stall; fast QA cleanup meant zero heartbeat events, so no new CPU inference about a slow launch is possible. Draft PR #51 adds CPU-correlated columns to the Node-only phase CSV analyzer: The QA checkout fast-forwarded cleanly to the analyzer commits |
|
2026-10-24 offline-safe agent handoff (documentation only) Windows device YASMAN was offline at the latest check. The maintainer expects to resume access around Tuesday 2026-10-27 09:00 WIB, but availability is not guaranteed. New persistent handoff: https://github.com/man612/wirebound/blob/fix/issue44-startup-trace-20261021/docs/qa/ISSUE44_RESUME_CHECKPOINT_2026-10-24.md The pre-handoff runtime/code baseline was Critical evidence: The 18,284-ms v6 startup outlier had a 5,899-ms heartbeat delay but no CPU fields. Subsequent 12/12 v7 starts were fast and produced no CPU heartbeat records before cleanup. Root cause UNKNOWN. Do not repeat fast-series testing without purpose or equate main-process CPU with all Electron processes. When access returns: check Desktop Commander/session/process state once, inspect Windows HEAD and clean working tree (last verified This is a handoff note, not a readiness claim or merge request. |
Offline QA correctness follow-up — 2026-10-24 (no Windows access)A source-level, deterministic multi-navigation fixture exposed a false-positive reporting risk in QA-only change on Draft PR #51:
Verification: Running the actual fetched analyzer and test functions in a separate JS sandbox with emulated Node module dependencies produced 9/9 passing logical cases. NOT YET TESTED: native Open edge: the separate PowerShell Existing v6 18,284ms stall still has no CPU fields. The startup long-tail root cause remains unknown, and PR #51 remains DRAFT / issue #44 OPEN. No Windows remote calls, merge, release, installs, or benchmark runs occurred. |
2026-10-24 cross-PR integration audit (GitHub-only; no merge)Compared PR #50 P0 risk #1 — IPC: PR #51 adds asynchronous P0 risk #2 — React App: preserve PR #51's renderer marks + lazy Settings and PR #50's P1 risk #3 — agent notes: retain both independent QA handoffs in Full source-grounded preservation plan and target verification gates: https://github.com/man612/wirebound/blob/fix/ux-audit-10-items-20261020/docs/qa/PR50_PR51_INTEGRATION_CONTRACT_2026-10-24.md Status: Documentation only in PR #50 branch; no cross-branch merge/rebase, production source edit, Node/Windows/browser test, NSIS build, or USB test was carried out. Keep #50/#51 Draft, #44/#48 Open. The planned Tue Oct 27 Windows restart is not confirmed availability. |
|
Cross-workstream heads-up only (no changes on PR #51): source-level Gnirehtet lifecycle races were reproduced using fake ADB/process dependencies and tracked separately at #53 and documentation-only Draft PR #54 . The |
2026-10-25 merge-readiness audit: exact HEAD CI is RED (real lint error)Rechecked current Draft PR HEAD
Exact source: Recommendation: keep this PR Draft/unmerged until real lint is fixed, all head checks pass, and representative Windows startup evidence is collected. No branch code or host machine was touched by this review. |
2026-10-28 CI blocker patch and QA boundary (unmerged)Addressed the exact previous hosted-Windows lint failure in No new GitHub Actions run/check is currently associated with the updated SHA. The maintainer's Windows PC was reachable, so an isolated F:\Wirebound-Lab\qa-pr-blockers-20261028 checkout was created at this exact HEAD. Thus lint blocker is patched in source but NOT yet demonstrated green. PR remains Draft; root cause of issue #44 (15–57-second startup tail) and physical startup QA remain open. Recheck actual CI on current HEAD; do not claim older run 39926342753 validates this commit or merge based on this note. Current |
Exact-head hosted Windows CI verifier PASS — 2026-10-28The corrected startup branch HEAD The temporary verifier PR #64 is being closed without merge; the original startup PR #51 remains Draft/UNMERGED and currently dirty vs latest main, and issue #44's long-tail 15–57 s Electron startup delay remains unresolved. Real native packaged startup timing and one-device USB/VPN checks are still needed; no claim that hosted CI measured the observed startup slowdown. The maintainer's slow Windows PC was not used for this CI. Preserve current main's ADB issue #56/audit issue #53 |
|
2026-11-10 integration checkpoint: The independently useful ASAR payload verification and packaging-input exclusion originally developed in this startup-investigation branch were extracted into focused PR #69, whose Windows CI (including deliberate byte-corruption detection and package smoke) passed; #69 was squash-merged into |
Purpose
Investigate intermittent Windows Electron startup / renderer readiness in #44 with opt-in, privacy-limited instrumentation and a reproducible Windows cold-start harness. This PR is diagnostic tooling, not a claimed fix. It is intentionally separate from the ten UX improvements in PR #50.
Changes
src/main/startupTrace.ts: append JSONL lifecycle events only ifWIREBOUND_QA_STARTUP_TRACEis explicitly set to an absolute file path. Fixed event names, times, status flags/codes and React root child count only; never capture DOM text, device IDs, paths, URLs, settings, traffic or IPC payloads.src/main/window.ts: track window creation/show, page load initiation/completion/rejection,did-fail-load,render-process-gone,dom-ready,ready-to-show, and a QA-only delayed React-root probe. No automatic reload.src/main/index.ts: track Electron readiness, bootstrap/window/tray/IPC/ADB milestones, runtime-path and settings-load durations; report previously unobserved bootstrap rejection.src/main/appPaths.ts: trace synchronous bundled ADB fingerprint/verification/cache-copy phases (only milestone timings and number of files copied, never paths or device data). Slow disk access is a hypothesis, not a confirmed root cause.scripts/qa/electron-cold-start.ps1: repeat cold-starts with fresh isolated APPDATA/LOCALAPPDATA, no remote debugging, and stop only the executable it launched after checking its path. The wait-time range is now 5–120 seconds.Windows QA: distinguish observed timeouts from persistent failures
Windows 11 Pro (build 26100), locally packaged Electron 44.4.1, unsigned QA installers; real VPN never started.
main+ identical trace, separately built and installed NSISapp.asarvs its unpacked counterpartAn intermediate QA retry rejected
-WaitSeconds 65due to a former 60-second parameter limit; this was a harness error before any app startup, now fixed. The timeouts are intermittent and not consistently reproducible. They do not prove a permanent renderer crash, an NSIS defect, or a regression caused by PR #50. ADB was unavailable during one successful unpacked startup, so an ADB causal link is also unproven.Validation
npm run typecheck: PASSnpm test: 50/50 PASS, including 4 new tracing testsnpm run build: PASSnpm run lint: 0 errors, 54 warnings; warning cleanup not in scopeNotSignedand never published.8449d8d: SUCCESS (workflow run39708440953). Local PowerShell syntax checks and 8/8 sequence tests also passed.Decisions / remaining investigation
Keep issue #44 open. Before attributing a cause or changing the app, collect safe OS scheduling, disk latency and Windows Defender/App Control evidence (without disabling security), and investigate the latest genuine 45-second installed renderer-not-ready observation, alongside the reproducible QA-tool false-negative case, across comparable conditions. Official Electron documentation distinguishes
ready-to-show(first paint) fromloadFile()anddom-ready(navigation/DOM readiness).No dependency upgrades, external releases, hardware VPN actions, speculative reload loops or merge to
mainin this PR.2026-10-21 follow-up — fixing QA false negatives and preserving genuine timeouts
A second local Windows investigation found two defects in the test harness, not in the Wirebound VPN service:
window-showncan occur later. The earlier runner only acceptedvisible: trueat the time of the single root probe, wrongly timing out if window show happened afterward. One UX run had React mounted at 4.034s and window shown at 12.693s, but the old runner called it a failure after 45 seconds.taskkill /T /Fmay appendrender-process-gone: killedafter a successful startup; analyzing every event irrespective of order erroneously marks that launch failed.Fix: a chronological, independently tested state machine now requires both a populated React root and a
window-shownevent in either order before a fatal event. The report and new optional process/Defender resource-sampling harness are included in commit34e93c5. All 8/8 PowerShell readiness tests pass, and the trace summarizer was run over actual stored QA timelines.main+ trace, 6 startswindow-createdat 16.5s,did-start-loadingat 20.6s, nodom-ready/show/root by cutoffWindows Defender was not disabled. Numeric sampled Defender CPU increased more during some longer startup windows, but comparisons use unequal observation durations, and the corrected timeout window had 0 Defender operational event IDs recorded. No causal Defender or Windows disk claim can be made. Do not suggest antivirus exclusions or an unconditional renderer reload.
This PR remains a draft instrumentation/QA correction, not a final fix of issue #44. Keep the issue open; dependency upgrades remain deferred.
2026-10-22 — diagnosed local ASAR corruption; added a strict packaging gate
During an instrumented local unpacked build, Electron Builder exited 0, yet the packaged application exited 1 before main-module startup. Independent inspection revealed an actual inconsistent
app.asarpayload/header: the packed QA report entry declared 16,612 bytes while its source had grown to 16,974 bytes during packaging; accounting for ASAR's fixed 8-byte prefix, later payload offsets were displaced by the same 362 bytes. The archive's extractedpackage.jsoncontained part of renderer HTML/CSP, not valid JSON. This is strong evidence of packaging from changing input files, separate from other intermittent startup stalls.A new
scripts/qa/verify-packaged-asar.cjsverifies every embedded SHA-256-protected payload, not only the archive header or a few files, and checks the manifest plus compiled Electron entrypoints. It correctly rejects the corrupted archive (3,969 inspected; 12 failures) and accepts a known-good prior build (3,967; 0 failures). A separate Node.js synthetic corruption test passes (valid archive accepted, one-byte-tampered archive rejected).Prevention in commit
c98ddd6:electron-builder.ymlexcludesdocs/**, which do not belong in runtime packaging.package:checkruns the validator's regression test before packing and scans the actual built archive after packing.build:unpackandbuild:winalso fail if ASAR integrity is invalid. No dependencies or network security settings changed.Frozen clean worktree QA: Windows
npm run package:checkexit 0; 3,960 ASAR payloads valid / 0 mismatches, QA docs confirmed absent and main module/manifest present. The verified unpacked app then passed 3/3 isolated cold starts with no manual reload or DevTools flag: React root probes at 11.014s, 2.619s, 2.564s respectively. Typecheck, 50/50 Vitest, Node corruption test, 8/8 PowerShell readiness tests, and local lint (0 errors, 54 warnings) also passed. Details recorded in8449d8d.Boundary: This addresses the distinct malformed local ASAR but does not establish a full fix for #44, because other previously healthy archives experienced intermittent BrowserWindow and renderer loading delays. The first integrity-guard commit was validated initially on unpacked Electron only. A subsequent same-code locally rebuilt NSIS installer has now been tested as described below; physical Android VPN validation on this branch remains outstanding. No release or merge was done. Keep this PR in draft and keep issue #44 open.
2026-10-22 — Installed NSIS QA and mandatory GitHub Actions ASAR gate
Commit
7cf476acloses an important CI coverage gap: the prior hosted Windows workflow invokednpx electron-builder --win --dirdirectly, bypassingnpm run qa:asardespite the latter being part of localpackage:check. The workflow now executesnpm run qa:asar:testbefore packaging andnpm run qa:asarafter packaging. A green CI result will now actually assert the embedded ASAR's payload hashes. No dependency changes.The same commit adds
scripts/qa/nsis-installed-smoke.ps1, a manual safety-guarded Windows installer test. It refuses to touch a machine with an existing default/registered Wirebound installation or running Wirebound process, silently installs to an isolated directory, compares installed and unpacked ASAR SHA-256 values, checks every embedded SHA-256-protected file, invokes the existing chronological cold-start harness with fresh settings profiles, then silently uninstalls its own QA installation. It reports a nonzero status if install, integrity, startup or cleanup fails. This manual GUI test is not claimed as a headless CI test.Exact Windows evidence:
npm run build:winexit 0 (unsigned local NSIS, SHA-256B5CC8A6A69682E65AECD7E36A6C0B4D9140911085191E44FB6FE972D62C2365E, not a public GitHub asset checksum); embedded ASAR guard 3,960 checked, 0 mismatches. The installed ASAR SHA-256 equaled the unpacked reference from the same build.nsis-installed-smoke.ps1: an additional 2/2 cold starts passed, full installed ASAR hash verification, NSIS uninstall exit 0, no residual executable or modification to default user install.git diff --checkclean.Hosted GitHub Actions verification: run 39710391308 on this exact commit PASSED. Job
verify-windowsseparately confirmed ASAR corruption regression PASS, Electron Builder package smoke PASS, and packaged ASAR payload integrity PASS, plus typecheck and all unit tests.These 8/8 successful installed trials increase confidence in the guarded build and manual installer procedure, but do not establish a permanent resolution of intermittent Electron startup #44. Some previous valid builds timed out, so this PR stays DRAFT with no merge, dependency upgrade, antivirus modification, real Android VPN retest or publication.
Complete dated investigation and reproduction steps.
2026-10-22 — Intermittent startup measured even on valid ASAR; QA-only event-loop heartbeat
Important update to #44: A clean, SHA-256-verified Windows unpacked build (3,960/3,960 ASAR entries valid) completed 8/8 fresh-profile 70-second startup tests, yet one showed its window only after 24.716s, vs 0.576–2.147s for the other seven. That outlier spent 5.275s creating
BrowserWindowand 11.209s loading the renderer. This confirms slow startup persists independently of the separate malformed-ASAR packaging failure.New commit
8585767implements opt-in QA-only main-process heartbeat, triggered only when the absoluteWIREBOUND_QA_STARTUP_TRACEfile setting is present. It records numeric timer lateness, never user/device/path content, unrefs its interval, and self-stops after two minutes. It does not change normal startup or add reload loops. Commitcb48e26updates the phase summarizer and evidence document.Rebuilt Windows unpacked executable with integrity verification again passed 3,960/3,960 files, then 8/8 more cold starts succeeded. This time one outlier needed 20.144s until the window showed (other seven 0.598–0.894s). The event-loop heartbeat on that outlier recorded 2,053ms, 7,642ms, and 945ms delayed ticks, during which native icon/window setup and renderer navigation were also slow. This demonstrates main-process timer starvation or OS scheduling delay; it does not prove the exact cause. Renderer
dom-readyoccurred 1.739s before ADB server readiness in that trial, so ADB readiness cannot be assumed to block rendering.Quality gates on the previous
cb48e26head: TypeScript typecheck, 52/52 Vitest unit tests, full Windows unpacked build, 3,960 verified ASAR payloads, local lint 0 errors (56 warnings), PowerShell script syntax and trace re-analysis pass. Windows hosted CI #39714854505 SUCCESS, including unit tests, package smoke, ASAR regression and payload integrity steps. QA process cleanup confirmed; Git checkout clean.Status: still DRAFT; keep issue #44 OPEN. Valid archives can still have 20–25-second startups even when eventual readiness tests pass. No signing, merge, release, dependency upgrades, antivirus changes, unconditional reloads or physical device VPN test on this branch. Detailed chronology.
2026-10-23 — counterbalanced same-binary Windows icon A/B: 48/48 starts pass, no end-to-end benefit
Goal: determine whether synchronously decoding the frameless BrowserWindow icon is a necessary contributor to #44's 20–25-second intermittent startup, before making any visible/production UX change.
Commit
3d588b8added strictly opt-in QA-onlyWIREBOUND_QA_SKIP_WINDOW_ICON=1, accepted only if an explicit absoluteWIREBOUND_QA_STARTUP_TRACEfile path is set. Normal application launches still decode and display the icon exactly as before. The cold-start harness accepts-SkipWindowIcon, records the mode, and the newscripts/qa/compare-window-icon-startup.ps1executes balanced runs using one identical unpacked Windows executable. This is diagnostic code, not an icon removal or a GPU flag change.Experimental setup: Windows 11 QA host YASMAN;
npm run build:unpackpassed from frozen3d588b8source, with 3,960/3,960 embedded ASAR SHA-256 payloads valid. ASAR SHA-256:86E1BC55A90A4373C7A0ABD030B4766813110BD693D9803C8E07A66337FD360C. No physical Android VPN, antivirus setting or user install was touched. Each launch used a distinct APPDATA/LOCALAPPDATA, 70-second readiness cutoff, no manual reload.The first 24 launches alternated
normal → skip → skip → normalfor six balanced blocks. The second 24 reversed the order (skip → normal → normal → skip). All 48/48 starts passed (24/24 per mode), with an independently verified visible window and populated React root.window-shownnew BrowserWindow()The first trial of the normal-first series was slow (4.181s, heartbeat 2.173s late), and the first trial of the skip-first series was also slow (2.816s, heartbeat 0.931s late). Hence slow initial startup can occur even when icon decoding is completely bypassed. Skipping the icon saves ~60ms in the constructor's median, but there was no overall median window-show improvement; the skip mode actually had a slightly worse p90 in this modest sample. Neither group reproduced the earlier 20–25s rare outlier, so there is no statistical or causal claim of permanent #44 resolution.
Decision: retain the normal Wirebound icon and keep #44 OPEN. The experiment rules down native icon decoding as a necessary explanation for the long tail, but does not identify OS scheduling, module load, GPU or native window implementation as the sole cause.
Commit
47aa9b4adds the reversed-run switch, another default-on-icon safeguard test, and a complete reproducible report. Local Windows validation on these changes: 55/55 Vitest, typecheck,npm run build:unpack, ASAR payload integrity 3,960/3,960, PowerShell parser,git diff --checkall PASS; lint 0 errors / 54 warnings on the same code before the last test-only addition. Hosted Windows CI run #39887635308 on exact latest commit47aa9b4is SUCCESS, with separately verified lint, typecheck, unit tests, renderer/main build, ASAR corruption regression, Windows packaging smoke, and packaged ASAR SHA-256 integrity steps.No merge, dependency upgrade, production icon alteration, network/security exception, GPU flag, Android VPN action, signed installer or release.
Full report and exact A/B commands.
2026-10-23 — QA profile isolation corrected; trace overhead and launch-gap long tail
New observation: On a SHA-256-verified unpacked Windows executable, a controlled launch-gap investigation with a 2-second vs 20-second delay between starts showed no consistent improvement from waiting. Unscored warm-up 55.257s to window, six 2s-delay starts 6/6 eventually visible (one 51.232s outlier, median 751.5ms), and six 20s-delay starts 5/6 visible by 70s (one still lacked
dom-ready, median among five passes 710ms). On the timeout trial Electron's main module started at 60ms,window-createdat 336ms, and renderer loading began at 376ms, but there was nodom-readyor window show before the 70s QA cutoff. The heartbeat was initially delayed 17.626s yet later resumed near-normal ticks for tens of seconds. This further establishes an intermittent renderer/navigation hang-like timeout without proving a permanent hang or its root cause.Instrumented vs uninstrumented, externally measured: Added a Windows API
IsWindowVisibleprobe so the same executable can be tested withWIREBOUND_QA_STARTUP_TRACEcompletely off. In an initial, not-yet-fully-profile-isolated A/B series, trace-first starts showed 5/6 visible within 70s, trace-off 6/6, while the reversed series showed 6/6 both modes. An untraced warm-up took 57.071s, demonstrating that severe long-tail startup can occur without our trace writes. The original A/B runner also wrongly treated a missing late React probe as a failure in one externally visible trace-on launch; fixed to score external visibility equivalently for both modes. Neither this nor the limited timing difference proves tracing has no overhead or is itself causal.Important correction to earlier QA safety claims: Windows Electron/Chromium subprocesses were found to use the ordinary roaming Wirebound
userDatadirectory despite our earlier harness changingAPPDATA/LOCALAPPDATA. The purported temporary roamingappdatadirectory was empty. Consequently, older descriptions of fully isolated fresh profiles were inaccurate, and those timing results may share Chromium caches/settings. We inspected only directory metadata, not user content, and did not delete or reset the existing roaming profile. This is a methodological and safety correction, not a claim that prior user-data writes can be reversed.Fix in
1a0e2cf: Strictly QA-onlyWIREBOUND_QA_PROFILE_ISOLATION=1and absoluteWIREBOUND_QA_PROFILE_DIRoverride Electronapp.setPath('userData')andsessionDatabefore app ready, independent of whether tracing is enabled. Invalid explicit QA paths fail closed; ordinary app startup is unchanged. Updated cold-start runner and newly committed balanced launch-gap / trace A/B tools use this verified isolation.Windows verification on this commit: typecheck PASS, 58/58 Vitest PASS (three QA profile gate tests added), lint 0 errors / 54 warnings,
npm run build:unpackPASS, embedded ASAR integrity 3,960/3,960 payload hashes match. An explicit QA smoke verified profile created with 16 entries, renderer and all four Chromium subprocesses used the QA path, no process remained. Updatedelectron-cold-start.ps12/2 PASS, both created separate populated QA profiles. With corrected independent userData isolation, an 8 scored trial trace-on/off A/B (two counterbalanced blocks, external window detection) showed 4/4 visible with tracing and 4/4 visible without, median external show 1,069ms trace-on vs 1,209ms trace-off, no 50–70s outlier. Too few trials to infer equivalence or eliminate intermittent #44.Evidence/docs in
32dfa67: full dated QA report. This is unpacked-only QA, not a fresh installed NSIS or physical Motorola VPN retest on this head. No dependency upgrade, security changes, public release, merge or normal-user feature changes. Issue #44 remains OPEN; PR remains DRAFT. Hosted Windows CI on exact latest head `32dfa67` SUCCESS, workflow #39926342753, with individually verified Lint, Typecheck, Unit tests, Build renderer/main, ASAR corruption guard test, Package smoke and packaged ASAR SHA-256 integrity steps.