Files
homarr/qa/release-v2/reports/performance-01/report.md
T

7.8 KiB

performance-01: Cold and warm board load

Metadata Value
Status blocked
Wave performance
PR refs #6555, #6545
Personas Avery Admin
Boards qa-grid-24, qa-widgets-12
Profiles main-writable
Chromium viewports mobile-375, desktop-1440
Zoom 100%
Input mouse
Widget kinds None
Artifact directory /home/habs/.codex/worktrees/8ba8/homarr/.screenshots/release-v2/performance-01
Candidate SHA f57a660088
URL / actual port http://127.0.0.1:37137 / 37137
Runtime profile / flags main-writable; DEMO_MODE=true, DEMO_READ_ONLY=false, UNSAFE_ENABLE_MOCK_INTEGRATION=true
Executed persona Avery Admin
Browser session ID qa-v2-performance-01
Timestamp 2026-08-31T18:17:56.112Z
Executed viewport / input / zoom mobile-375 / mouse / 100%

Dogfood evidence

Case ID Status Evidence Observed Expected
PE-001-BASELINE blocked browser artifacts The application entry repeated redirects until Chromium stopped navigation; the assigned flow was not reachable. Capture repeatable cold and warm timing, request, render, memory, and console baselines with candidate metadata.
PE-001-THRESHOLD blocked browser artifacts The application entry repeated redirects until Chromium stopped navigation; the assigned flow was not reachable. Measure the packet at every assigned viewport, zoom, input, board, and profile against the documented threshold.
PE-001-STRESS blocked browser artifacts The application entry repeated redirects until Chromium stopped navigation; the assigned flow was not reachable. Exercise dense data, repeated interaction, long-session, latency, and failure stress that applies.
PE-001-RECOVERY-EVIDENCE blocked browser artifacts The application entry repeated redirects until Chromium stopped navigation; the assigned flow was not reachable. Verify recovery after stress and link trace, screenshot, network, memory, and cleanup artifacts.

Performance measurements and limitations

No valid feature timing could be recorded because no application document rendered. Cold/warm, polling, rendering, memory, and recovery measurements remain blocked.

Independent reproductions

The common routing failure was independently reproduced by qa-v2-preflight-01; the corresponding tracked packet contains its own browser evidence.

Findings

RV2-P1-001 — P1: locale rewrite causes an infinite browser redirect

Preconditions: candidate f57a660088, main-writable, mobile-375, 100% zoom, mouse, fresh named Chromium session qa-v2-performance-01.

  1. Launch a fresh Chromium context with the Chromium argument --no-sandbox.
  2. Set the assigned viewport and open http://127.0.0.1:37137 or its authentication entry.
  3. Observe repeated document requests to the same route.
  4. Wait until Chromium displays ERR_TOO_MANY_REDIRECTS or chrome-error://chromewebdata/.
  5. Compare the result with the independently reproduced preflight evidence.

Expected: the application renders the assigned entry, permitting authentication and the packet flow. Actual: the redirect loop prevents the application from rendering. Reproducibility: reproduced independently by the preflight agents. Console output was empty; network and visual evidence are linked below.

Artifacts

Mutations and persistence

No credentials were submitted and no product mutation occurred. Reload and fresh-session retries reproduced the routing failure, so application persistence was not reachable.

Blockers and gaps

Every non-evidence case listed as blocked remains untested beyond the routing entry. No blocked cell is treated as passed.

Cleanup

The named browser session was closed by the browser agent. Artifacts remain under the untracked packet directory; no secret values were captured.