homarr/qa/release-v2/reports/performance-03/report.md

performance-03: Widget network and render budget

Metadata	Value
Status	blocked
Wave	performance
PR refs	#6502, #6555
Personas	Ingrid Infra, Maya Media
Boards	qa-widgets-04, qa-widgets-07, qa-widgets-12
Profiles	main-writable, degraded
Chromium viewports	mobile-320, desktop-1440
Zoom	100%
Input	mouse, touch
Widget kinds	None
Artifact directory	/home/habs/.codex/worktrees/8ba8/homarr/.screenshots/release-v2/performance-03
Candidate SHA	f57a660088
URL / actual port	http://127.0.0.1:46777 / 46777
Runtime profile / flags	degraded; DEMO_MODE=true, DEMO_READ_ONLY=false, UNSAFE_ENABLE_MOCK_INTEGRATION=true
Executed persona	Ingrid Infra
Browser session ID	qa-v2-performance-03
Timestamp	2026-08-31T18:30:29.480Z
Executed viewport / input / zoom	mobile-320 / mouse / 100%

Dogfood evidence

Case ID	Status	Evidence	Observed	Expected
PE-003-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-003-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-003-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-003-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, degraded, mobile-320, 100% zoom, mouse, fresh named Chromium session qa-v2-performance-03.

1. Launch a fresh Chromium context with the Chromium argument --no-sandbox.
2. Set the assigned viewport and open http://127.0.0.1:46777 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

• close-mouse-entry.txt
• close.txt
• console-mouse-entry.txt
• console.txt
• errors-mouse-entry.txt
• errors.txt
• network-mouse-entry.txt
• network.txt
• open.txt
• performance-03-320x568-100-mouse-entry.png
• performance-03-320x568-100-mouse.png
• screenshot.txt
• setup.txt

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.