Repository navigation
Conversation
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.003155%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: 194.03 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" [2.538, 3.039, 5.543, 8.547, 11.551, 14.054, 17.058, 20.061, 22.565, 25.567, 28.572, 31.077, 34.081, 37.085, 39.587, 42.591, 45.593, 48.097, 51.103, 54.107, 56.61, 59.613, 62.618, 65.119, 68.124, 71.13, 73.631, 76.635, 79.64, 81.142, 82.143, 85.146, 88.149, 90.652, 93.655, 96.658, 99.161, 101.163]
y-axis "CPU percent" 0 --> 500
line [123.74, 147.7, 175.92, 105.72, 127.91, 117.67, 7.99, 0, 4, 4, 5.99, 0, 0, 2, 3.99, 4, 5.99, 0, 8, 0, 4, 2, 2, 0, 0, 5.99, 4, 63.99, 101.94, 99.91, 135.84, 141.96, 121.85, 115.85, 87.91, 119.88, 19.97, 210.05]
xychart-beta
title "Base memory: RSS then PSS"
x-axis "Elapsed seconds" [0.036, 2.538, 3.039, 5.543, 8.547, 11.551, 14.054, 17.058, 20.061, 22.565, 25.567, 28.572, 31.077, 34.081, 37.085, 39.587, 42.591, 45.593, 48.097, 51.103, 54.107, 56.61, 59.613, 62.618, 65.119, 68.124, 71.13, 73.631, 76.635, 79.64, 81.142, 82.143, 85.146, 88.149, 90.652, 93.655, 96.658, 99.161, 101.163, 101.69]
y-axis "Memory MiB" 0 --> 500
line [12.09, 125.66, 137.14, 161.6, 163.95, 170.72, 166.2, 176.33, 145.85, 144.83, 144.83, 145.23, 145.23, 145.23, 145.61, 146.55, 147.1, 147.1, 147.07, 142.05, 140.07, 140.17, 140.24, 140.32, 140.39, 140.36, 137.36, 136.67, 138.56, 152.95, 270.53, 198.43, 189.12, 168.23, 168.64, 154.09, 158.8, 148.72, 192.34, 0]
line [8.98, 122.1, 133.58, 158.04, 160.4, 167.15, 162.64, 172.9, 142.24, 141.22, 141.22, 141.63, 141.63, 141.63, 142, 142.94, 143.49, 143.49, 143.46, 138.43, 136.45, 136.55, 136.62, 136.7, 136.77, 136.75, 133.75, 133.08, 134.86, 149.34, 266.89, 194.74, 186.53, 165.1, 164.97, 150.42, 155.13, 144.95, 188.75, 0]
HEADxychart-beta
title "HEAD CPU"
x-axis "Elapsed seconds" [1.54, 2.04, 3.041, 4.544, 6.047, 7.548, 9.049, 10.552, 12.054, 14.056, 15.559, 17.059, 18.562, 20.064, 21.565, 23.066, 24.566, 26.067, 27.569, 29.07, 30.572, 32.074, 33.576, 34.577, 35.078, 36.581, 38.084, 39.586, 41.589, 43.092, 44.594, 46.097, 47.597, 49.099, 50.602, 52.104, 53.606, 54.608]
y-axis "CPU percent" 0 --> 500
line [1.99, 0, 0, 2, 0, 2, 0, 115.83, 121.8, 171.78, 165.81, 53.9, 185.75, 93.82, 29.96, 155.9, 96.07, 72.02, 37.95, 41.95, 113.8, 127.7, 131.84, 113.95, 129.79, 153.63, 143.68, 147.82, 135.69, 95.8, 9.99, 147.72, 59.92, 4, 113.79, 175.56, 137.76, 197.66]
xychart-beta
title "HEAD memory: RSS then PSS"
x-axis "Elapsed seconds" [0.038, 1.54, 2.04, 3.041, 4.544, 6.047, 7.548, 9.049, 10.552, 12.054, 14.056, 15.559, 17.059, 18.562, 20.064, 21.565, 23.066, 24.566, 26.067, 27.569, 29.07, 30.572, 32.074, 33.576, 34.577, 35.078, 36.581, 38.084, 39.586, 41.589, 43.092, 44.594, 46.097, 47.597, 49.099, 50.602, 52.104, 53.606, 54.608, 55.091]
y-axis "Memory MiB" 0 --> 500
line [12.31, 64.45, 64.45, 63.44, 63.44, 63.44, 63.44, 63.44, 118.36, 127.34, 163.26, 185.68, 155.59, 186.27, 151.38, 185.73, 172.42, 154.09, 163.93, 149.54, 153.83, 185.16, 162.04, 190.1, 281.69, 203.11, 214.46, 188.93, 162.6, 178.73, 159.79, 153.74, 207.21, 183.14, 164.11, 189.99, 190.75, 192.48, 199.38, 0]
line [9.16, 60.98, 60.98, 59.97, 59.97, 59.97, 59.97, 59.97, 114.96, 123.95, 160.06, 182.31, 152.14, 182.78, 147.84, 182.11, 168.81, 150.44, 160.64, 145.54, 150.19, 181.45, 158.48, 186.5, 277.71, 199.46, 210.85, 185.27, 158.99, 175.36, 156.14, 150.09, 204.35, 179.5, 160.46, 186.45, 186.62, 189.38, 196.05, 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. |
Retained child Window timer and EventTarget methods now resolve the receiver's captured native binding instead of acting on a replacement iframe realm. Listener argument conversion cannot redirect a captured Window operation into a replacement document.
Includes the required EventTarget routing in the same PR. Native and CDP regressions cover retained globals, timer registration/cancellation, event registration/dispatch, borrowed methods, reentrant conversion, and iframe removal/reinsertion.
Based directly on main; no prerequisite PRs.
Validation before commit: