Repository navigation
fix(fetch): settle bounded post-load render work - #1432
lanyue-llk wants to merge 1 commit into
Conversation
87940e6 to
6b6b3ba
Compare
edf45a7 to
d6de89d
Compare
d6de89d to
1d827c9
Compare
Sequential Navigation Soak A/B✅ HEAD completed the 200-navigation resilience and memory observation. One browser process, one target, and one CDP session navigate CSDN → SegmentFault → Huaban → example.com repeatedly. This run issued 200 Common ancestor Session resilience
A public-page failure is reported separately from an unrecoverable session. The soak requires all navigation attempts, zero failed recovery, zero lifecycle/network ordering violations, and complete resource evidence. Process-tree memory
HEAD memory by 50-navigation quarter
Raw reports and per-navigation boundary samples: workflow run and full Public-site timing and memory are observational. Use the A/B deltas and trend shape as evidence, not as a deterministic performance threshold. |
CI Regression ReportSource CI run · source state at render:
Release regression — ✅ HEAD/base failures 0/0; raw binary +0.003169%Package and image size
Startup latency and PSS
Concurrency matrix
Frontend differential — ✅ 1,020/1,020 cases matched; 0 issues
Agent episodes · Moli vs Chromium — ✅ 8/8 Moli episodes passed; 0 failures
Runtime and CDP session contracts — ✅ 26 contract cases; 0 failures
CDP smoke — ✅ 52/52 groups passed; 621 scenariosWorkers: 4 · cumulative group time: 192.27 s · failed groups: 0
WebMainBench · 545 pages — ✅ 545/545 completed; 0 unexpected failures
Frozen HTML · Linux · Diagnostics: All artifact fields are parsed by the trusted default-branch renderer; missing or invalid inputs remain visible as unavailable. |
Spider Bench A/B✅ All benchmark browser service runs completed; results are informational. Public HEAD: 184 / 240 rows; 38 / 48 sites produced rows; 10 unexpected empty sites. ✅ Deterministic fixture contract is clean. Common ancestor Public 48-site run · informational
Public-site content, timing, and memory are noisy. This single A/B run reports evidence only; site outcome counts explain missing rows without treating them as a deterministic regression. CPU and memory timelinesThese are bounded 40-point views of the same complete process-tree samples used by the HTML report. CPU uses 100% per occupied logical core; memory lines are RSS first and PSS second when complete PSS samples are available. Basexychart-beta
title "Base CPU"
x-axis "Elapsed seconds" [1.585, 3.086, 4.587, 6.09, 7.593, 9.094, 10.095, 11.597, 13.099, 14.602, 16.104, 17.605, 18.605, 19.106, 20.607, 22.108, 23.611, 25.114, 26.616, 27.617, 28.617, 29.117, 30.62, 32.122, 33.625, 35.127, 36.629, 38.131, 39.633, 41.134, 42.637, 44.139, 45.14, 46.642, 48.144, 49.646, 51.149, 51.65]
y-axis "CPU percent" 0 --> 500
line [117.85, 42.01, 123.95, 153.66, 165.62, 82.01, 171.82, 95.77, 69.92, 143.8, 127.65, 4, 0, 5.99, 124.06, 21.98, 173.77, 127.62, 153.88, 139.85, 108.03, 105.96, 137.79, 161.59, 111.78, 6, 145.94, 107.91, 95.98, 143.84, 141.63, 15.98, 11.99, 55.92, 111.86, 47.95, 123.79, 197.52]
xychart-beta
title "Base memory: RSS then PSS"
x-axis "Elapsed seconds" [0.083, 1.585, 3.086, 4.587, 6.09, 7.593, 9.094, 10.095, 11.597, 13.099, 14.602, 16.104, 17.605, 18.605, 19.106, 20.607, 22.108, 23.611, 25.114, 26.616, 27.617, 28.617, 29.117, 30.62, 32.122, 33.625, 35.127, 36.629, 38.131, 39.633, 41.134, 42.637, 44.139, 45.14, 46.642, 48.144, 49.646, 51.149, 51.65, 52.186]
y-axis "Memory MiB" 0 --> 500
line [12.46, 114.11, 130.24, 137.53, 165.19, 161.28, 176.05, 181.28, 167.02, 164.95, 182.46, 162.1, 149.45, 147.92, 148.13, 175.43, 142.68, 168.46, 199.8, 190.26, 159.82, 274.98, 219.25, 205, 231.55, 159.71, 163, 176.56, 158.57, 165.77, 197.35, 251.57, 184.39, 169.21, 170.22, 183.92, 158.03, 180.57, 203.51, 0]
line [9.26, 110.51, 126.65, 133.91, 162.15, 157.62, 172.37, 176.15, 163.35, 161.27, 178.82, 158.43, 145.78, 144.25, 144.46, 171.77, 139.01, 164.91, 196.15, 186.6, 156.15, 272.04, 215.21, 201.4, 227.87, 155.9, 159.33, 172.9, 154.89, 162.07, 193.34, 247.91, 180.69, 165.51, 166.51, 180.22, 154.3, 176.97, 199.86, 0]
HEADxychart-beta
title "HEAD CPU"
x-axis "Elapsed seconds" [1.541, 3.044, 4.545, 5.545, 6.046, 8.047, 9.548, 11.051, 12.553, 14.056, 15.56, 17.062, 19.174, 20.676, 22.677, 24.179, 25.682, 27.183, 27.684, 28.684, 30.185, 31.688, 33.189, 34.69, 36.693, 38.195, 39.696, 41.199, 42.7, 44.201, 45.702, 47.205, 48.705, 50.708, 52.211, 53.714, 55.216, 56.217]
y-axis "CPU percent" 0 --> 500
line [63.84, 125.78, 113.96, 183.77, 153.9, 163.99, 155.7, 155.55, 131.62, 141.8, 107.88, 109.91, 57.89, 15.99, 0, 43.95, 129.87, 103.87, 105.75, 114.05, 129.88, 11.98, 0, 123.85, 129.82, 103.9, 65.95, 113.74, 141.84, 100.01, 15.98, 0, 4, 4, 127.79, 59.88, 107.85, 202]
xychart-beta
title "HEAD memory: RSS then PSS"
x-axis "Elapsed seconds" [0.039, 1.541, 3.044, 4.545, 5.545, 6.046, 8.047, 9.548, 11.051, 12.553, 14.056, 15.56, 17.062, 19.174, 20.676, 22.677, 24.179, 25.682, 27.183, 27.684, 28.684, 30.185, 31.688, 33.189, 34.69, 36.693, 38.195, 39.696, 41.199, 42.7, 44.201, 45.702, 47.205, 48.705, 50.708, 52.211, 53.714, 55.216, 56.217, 56.527]
y-axis "Memory MiB" 0 --> 500
line [12.57, 94.12, 137.13, 133.62, 148.96, 167.92, 169.77, 178, 174.16, 185.75, 182.65, 169.55, 153.64, 160.3, 146.16, 146.58, 157.97, 161.06, 231.44, 284.89, 197.27, 186.11, 167.31, 165.13, 158.91, 171.25, 154.25, 149.39, 190.23, 247.02, 192.95, 165.18, 163.82, 163.82, 163.82, 190.25, 152.29, 175.71, 205.51, 0]
line [9.24, 90.4, 133.51, 129.93, 145.22, 165.2, 165.84, 174.36, 170.58, 181.87, 178.82, 165.62, 149.74, 156.42, 142.31, 142.77, 154.21, 157.35, 227.72, 280.62, 193.58, 182.47, 163.58, 161.39, 155.17, 167.59, 150.52, 145.61, 186.68, 243.31, 189.21, 161.45, 160.09, 160.09, 160.09, 186.56, 148.57, 171.99, 201.83, 0]
Deterministic fixture · required contractThe fixture exercises 15 routes: 8 are expected to emit rows and 7 intentionally exercise empty, loading, or timeout behavior.
Full HTML, JSON, CSV, logs, and page snapshots: workflow run and full The public-web A/B is informational. The exact HEAD fixture contract runs as a separate required CI check; timing and public-site content deltas remain non-blocking. |
|
Closing after the consolidation audit. A fixed 20 ms / 16-task post-load drain has no stable product completion meaning and is intentionally excluded from #1501. |
A page can dispatch Load before an already queued first render turn mounts its visible application content. Native Markdown then snapshots the complete documentation shell but misses live tables or other content produced by that immediate render chain.
This change adds one bounded owner command after Load/Done. It consumes only the current document’s already queued animation frame and one-shot zero-delay timer work, including each task’s normal microtask checkpoint. It stops after 20 ms or 16 turns. Intervals, future business timers, idle callbacks, internal timers, and URL-specific rules remain outside the completion boundary.
The behavior test mounts a table through Load → requestAnimationFrame → setTimeout(0) → microtask. A five-second fallback and a repeating zero-delay interval verify that background work does not hold the result open. The tests run through the repository CI.
PR stack
GitHub dependency chain:
#1334 → #1335 → #1336 → #1337 → #1380 → #1428 → #1431 → #1432
This PR targets
codex/risk011-navigation-handoff, the head branch of #1431. Its Files changed view therefore contains only this bounded post-load render fix. Merge the stack from left to right. #919 is a separate historical combination and is not a dependency. #1429 targetsmainindependently because it only adds reusable comparison CI.