enricobuehler 7ab97bb1a3 feat(host): capture-stall watch — DWM-level self-diagnosis for the Exclusive-topology stutter ...

Field repro (Mounjay, still present on 0.9.0): the ~4 s double-jolt stutter
appears ONLY while the virtual display is the sole active display (Exclusive
topology) and stops the instant Windows switches to Extend — live, both ways.
Cross-project research (Apollo #179/#358/#368/#563/#776, VDD #36, Tom's HW)
points at the display/present path BELOW capture: an inactive-but-connected
DisplayPort head being periodically serviced (standby HPD/AUX/link events),
with a DWM software-vsync clock beat as the secondary (different-signature)
class. Neither ends in anything our recovery-side detector can see unless the
client actually loses data — so give the HOST a direct sensor at the ring:

- StallWatch (idd_push.rs): a >150 ms hole in DWM frame delivery counts as a
  capture stall only when the 8 preceding frames arrived within 400 ms —
  sustained >=20 fps flow, so an idle desktop, a caret blink, or a paused
  video can never trip it. Per-stall debug line; when stalls settle into an
  evenly-spaced multi-second cycle, one rate-limited WARN names the class:
  'capture stalls are METRONOMIC', with the topology=primary/extend and
  refresh-rate leads. Ring-recreate recovery gaps reset the watch (self-
  inflicted, already logged by the recreate path).
- The evenly-spaced-cycle detector moves out of punktfunk1.rs into
  metronome.rs (RecoveryCadence -> Metronome, unchanged logic + tests) so the
  IDR-serve detector and the stall watch share one implementation; the
  recovery WARN now cross-references the capture-stall lines.

Diagnosis map for an Exclusive-mode stutter log: 'slow display-descriptor
poll' = something holds the win32k display lock; 'capture stalls are
METRONOMIC' without it = DWM stopped composing (DP servicing / present
clock, below us); recovery-IDR METRONOMIC alone = frames flowed but clients
lost data. Verified: Linux tests+clippy+fmt clean; Windows (RTX box)
220/220 + clippy clean.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

2026-07-10 11:05:21 +02:00

..

pf-client-core

fix(security): anti-replay, 0600 client key, open redirect, supply-chain

2026-07-10 10:04:23 +02:00

pf-console-ui

feat(clients): tiered stats overlay everywhere — Compact/Normal/Detailed on every platform

2026-07-10 01:42:46 +02:00

pf-driver-proto

docs: repo-wide housekeeping — sync README & docs with the code as shipped

2026-07-10 09:13:42 +02:00

pf-ffvk

feat(clients/windows): port the Vulkan session client to Windows — session-always

2026-07-08 23:21:36 +02:00

pf-presenter

feat(clients): tiered stats overlay everywhere — Compact/Normal/Detailed on every platform

2026-07-10 01:42:46 +02:00

punktfunk-core

style: cargo fmt — settle comment/assert layout the last two fixes left unformatted

2026-07-10 10:20:40 +02:00

punktfunk-host

feat(host): capture-stall watch — DWM-level self-diagnosis for the Exclusive-topology stutter

2026-07-10 11:05:21 +02:00

punktfunk-tray

refactor(client): extract UI-agnostic plumbing into pf-client-core (phase 0)

2026-07-07 23:13:16 +02:00