Repository navigation
fix(html): preserve child meta refresh with shared scheduling - #1661
Merged
Merged
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. |
Spider Bench A/B✅ All benchmark browser service runs completed; results are informational. Public HEAD: 189 / 240 rows; 39 / 48 sites produced rows; 9 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.038, 2.04, 2.541, 3.546, 4.547, 5.047, 6.048, 7.548, 8.548, 9.549, 11.053, 12.054, 13.556, 14.557, 15.56, 17.06, 18.061, 19.563, 20.564, 22.066, 23.068, 24.069, 25.569, 26.57, 28.072, 29.074, 30.075, 31.578, 32.578, 34.081, 35.082, 36.083, 36.585, 37.586, 38.588, 40.089, 41.09, 42.593]
y-axis "CPU percent" 0 --> 200
line [17.96, 41.94, 79.89, 117.06, 82.01, 144.04, 129.79, 94.03, 109.97, 57.86, 31.92, 131.97, 25.95, 119.89, 99.77, 22.01, 57.9, 77.96, 87.8, 99.9, 109.97, 133.81, 119.99, 91.82, 89.92, 99.86, 109.76, 37.9, 17.99, 85.9, 45.96, 0, 2, 2, 135.86, 154.11, 85.8, 179.72]
xychart-beta
title "Base memory: RSS then PSS"
x-axis "Elapsed seconds" [0.037, 1.038, 2.04, 2.541, 3.546, 4.547, 5.047, 6.048, 7.548, 8.548, 9.549, 11.053, 12.054, 13.556, 14.557, 15.56, 17.06, 18.061, 19.563, 20.564, 22.066, 23.068, 24.069, 25.569, 26.57, 28.072, 29.074, 30.075, 31.578, 32.578, 34.081, 35.082, 36.083, 36.585, 37.586, 38.588, 40.089, 41.09, 42.593, 43.139]
y-axis "Memory MiB" 0 --> 500
line [13.07, 72.96, 103.34, 94.05, 106.71, 127.65, 139.06, 150.55, 150.43, 148.42, 134.26, 136.66, 145.53, 136.87, 151.21, 150.89, 116.19, 124.11, 166, 148.83, 246.27, 195.8, 182.93, 165.87, 146.96, 184.81, 146.67, 146.45, 136.1, 138.18, 176.87, 151.65, 127.02, 124.07, 125.13, 161.64, 158.63, 135.09, 163.07, 0]
line [9.18, 68.91, 99.3, 90, 102.71, 123.03, 134.96, 146.4, 146.34, 144.5, 130.37, 132.79, 141.79, 130.88, 147.52, 146.32, 112.49, 120.47, 162.35, 145.48, 242.73, 192.59, 179.36, 162.23, 143.35, 181.5, 143.12, 143.16, 132.52, 134.79, 173.32, 147.87, 123.44, 120.65, 121.72, 158.17, 154.93, 131.6, 159.48, 0]
HEADxychart-beta
title "HEAD CPU"
x-axis "Elapsed seconds" [1.535, 2.536, 3.037, 4.038, 4.538, 6.04, 7.543, 9.043, 10.545, 12.045, 13.545, 15.045, 16.547, 18.048, 19.55, 21.052, 22.554, 24.055, 25.558, 27.061, 27.562, 28.063, 29.565, 31.067, 32.57, 34.071, 35.571, 37.076, 38.579, 40.08, 41.581, 43.084, 44.586, 46.088, 47.595, 49.097, 50.598, 52.101]
y-axis "CPU percent" 0 --> 200
line [15.99, 89.9, 121.84, 121.86, 153.99, 127.78, 139.79, 80.01, 119.95, 112.03, 127.98, 6, 3.99, 0, 2, 2, 3.99, 125.81, 113.71, 127.72, 99.74, 111.85, 129.82, 123.76, 139.88, 123.89, 103.97, 71.95, 79.87, 89.98, 0, 63.95, 99.87, 99.88, 99.21, 103.75, 31.98, 131.68]
xychart-beta
title "HEAD memory: RSS then PSS"
x-axis "Elapsed seconds" [0.034, 1.535, 2.536, 3.037, 4.038, 4.538, 6.04, 7.543, 9.043, 10.545, 12.045, 13.545, 15.045, 16.547, 18.048, 19.55, 21.052, 22.554, 24.055, 25.558, 27.061, 27.562, 28.063, 29.565, 31.067, 32.57, 34.071, 35.571, 37.076, 38.579, 40.08, 41.581, 43.084, 44.586, 46.088, 47.595, 49.097, 50.598, 52.101, 53.223]
y-axis "Memory MiB" 0 --> 500
line [12.96, 79.01, 95.09, 114.98, 136.04, 126.43, 146.34, 142.16, 153.45, 140.44, 140.12, 145.72, 131.46, 116.95, 121.43, 120.43, 120.48, 120.37, 141.85, 135.62, 180.69, 249.27, 231.07, 183.41, 167.74, 146.45, 155.68, 143.6, 139.32, 177.18, 153.36, 143.14, 142.62, 160.84, 164.33, 164.46, 166.15, 147.09, 155.46, 0]
line [9.65, 75.7, 91.35, 111.54, 132.43, 123.04, 142.21, 138.62, 149.77, 136.76, 136.43, 142.04, 127.75, 113.22, 117.72, 116.66, 116.7, 116.59, 138.08, 131.96, 176.98, 245.58, 226.94, 179.71, 164.05, 142.8, 152.05, 139.94, 135.59, 174.31, 149.78, 139.52, 138.86, 157.21, 160.69, 160.69, 162.44, 143.27, 151.78, 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. |
CI Regression ReportSource CI run · source state at render:
Release regression — ✅ HEAD/base failures 0/0; raw binary +0.000735%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 — ⚪ artifact unavailable or invalidArtifact unavailable or invalid. See the source CI run for infrastructure details. 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. |
ldm0
force-pushed
the
fix/child-meta-refresh-1118
branch
from
October 20, 2026 22:10
7febf96 to
e60d48f
Compare
ldm0
changed the title
ldm0
force-pushed
the
fix/child-meta-refresh-1118
branch
from
October 25, 2026 07:43
66cf11b to
25b31c5
Compare
Process parser and script-created refresh declarations in order and retain them on their owning Document across load callbacks and adoption. Share candidate priority and deadline state between main and child documents, and arm child timers after owner load completes. Consume queued work by exact Document identity and revision, classify navigation when it fires, and keep the registered target URL. Reprocess same-value meta attributes using the matched Attr identity so XML case, namespaces, observer records, and refresh deadlines remain correct. Cover competing declarations, stale tasks, independent frames, load/adoption boundaries, sandbox/shadow handling, saved targets, and fragment navigation.
ldm0
force-pushed
the
fix/child-meta-refresh-1118
branch
from
October 25, 2026 18:49
fb50cdd to
f9497ec
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Child meta refreshes could be lost or reordered when load callbacks moved, removed, or inserted declarations. Zero-delay refreshes could navigate before the iframe owner's load event completed. Register declarations in parser/DOM processing order, retain them on their owning Document across adoption, and arm child timers after owner-load delivery.
Main and child Documents share
MetaRefreshSchedulerfor candidate priority, revisions, and deadlines. Shorter declarations replace slower ones; newly processed equal-delay declarations restart the delay. Repeated internal work and timer-post retries preserve the existing deadline. Queued work carries Document identity and revision, and consumes the saved navigation only after validation. Navigation type is chosen when the refresh fires while preserving the registered target URL, including exact-fragment behavior.Same-value HTML meta
contentandhttp-equivassignments retain semantic notifications independently of MutationObserver recording. Ordinary setters use document-aware qualified-name matching and the actual Attr local name and namespace. XML/XHTML case and observer filters stay correct, and writing a namespaced Attr throughsetAttribute()does not restart refresh timing.Regression coverage includes declaration order and competing delays, independent iframes, load/adoption boundaries, sandbox/shadow handling, stale selected tasks, saved target URLs, fragment navigation, same-value setters, XML case, and namespace identity. Page tests use the existing workflow deadline throughout selected-task waits.
Validation for
f9497ecc371d87bca11506e2d26b424c1269f216:cargo fmt --allcargo clippy --workspace --all-targets --all-features -- -D warningscargo nextest run --no-fail-fast: 20,828 passed, 19 skipped, default profile/parallelism, no retries.A separate compatibility gap recorded during review is child
pageshow -> document.open()losing a pending nonzero refresh while Chromium retains it. That issue is tracked separately.