With DevTools on (port or pipe), Chrome tells pages a program drives it, and
YouTube then shows "문제가 발생했습니다" after about a minute of video, which
spoilt every window on the gaming PC. Reproduced on Linux: the port alone,
with no command sent, breaks playback at ~40 s; without it, or with
--disable-blink-features=AutomationControlled, it plays on. The browser is now
started with that switch, and one that still reports webdriver is refused
before Jarvis is started.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
When loading the page again did not bring a player back, keep_room still
moved the missing player back to the start, the page script threw and the
stage stopped at the first window. Now a failed reload (or a refused
navigation) is recorded as "the video did not play again", only a playing
video is moved back (and the script checks the player exists), so the
window is measured as it is, not counted, and tried again up to the limit
before the stage goes on. The reload waits RELOAD_S for the video.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
On the gaming PC the player errored about 38 s into the first window with
Jarvis off; the kit had no way to notice, so every later window measured a
paused, empty player, and after the user reloaded the page the injected
counters were gone and the snapshot script threw, ending the stage early.
- The snapshot reports a lost page (counters gone, or the script could not
run while the page loaded) and the player's own error screen (first line
only, bracketed IDs removed) instead of throwing.
- Before each window the kit presses play on a stopped player and loads the
page again when that is not enough, or when the page was lost or errored.
- A window the player spoilt (error, reload, pause, ad, seek, buffering, no
frames) is measured again, up to 3 times in all, with the earlier attempts
and the fixes kept in the row; a lower quality or frame rate is not, since
a busy GPU can cause it.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- A window counts only when the player kept the asked quality and height
the whole time and played the source's 60 fps; a player stuck below
1080p is a stage error, not a note.
- Pauses, seeks and buffering are counted inside the page during the
window, so a pause that ended before the last snapshot no longer
passes as GPU stutter.
- A capped window whose cap found nothing to pause, ran no pause cycle,
or could not pause or resume a process is an error and does not count
for the cap.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
User decision (2026-11-11): the 95 % GPU cap is off by default because
gamemode_tune showed it did not lower nvidia-smi's utilisation and cost
6 to 10 % of the LLM's output. The worry behind it was a video stuttering
next to Jarvis, so the new on-demand stage video_drops measures that:
- A public Blender upload plays at 1080p60 in a throwaway Chrome/Edge
profile (removed afterwards), driven over DevTools with a small
standard-library WebSocket client, so no package is added to the
already built venvs.
- Each window counts the video's dropped frames (the player's own
counter) and the gaps over 50/100 ms between shown frames
(requestVideoFrameCallback); windows with an ad, a pause, the end or a
new video are kept but not counted.
- Rows: video alone, Jarvis idle (normal placement with the STT room and
1 GB for other programs), Jarvis busy (LLM answering, STT transcribing
ten speakers back to back) without and with the cap in A B B A order,
then the video alone again. The cap pauses the engine and the STT
worker only, never the browser.
- run_m0_video.bat runs just this stage.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>