Hacktoberfest 2026 : les issues que les mainteneurs ont marquées pour octobre, ouvertes et accessibles aux débutants. Parcourir les issues Hacktoberfest

Macos: Recording pipeline repeatedly stalls for 5–22 s (whole process), causing ~10% video loss and multi-second audio gaps

Ouverte
#2,366 1 commentaire 0 réactions 0 personnes assignées Voir sur GitHub

Les mainteneurs répondent en général sous 1 jour

Personne n'a encore pris cette issue.

Évaluation

Difficulté
5/5
Temps estimé
Plus d'une semaine
Accessibilité débutants
32/100
Type d'issue
Bug
Clarté
À clarifier
Activité
Active
Stack technique
macos, rust, tauri

Piste de recherche

Start with the attached cap-desktop.log and correlate the process-wide silent windows with video, microphone, and system-audio events. Trace the recording pipeline and shared runtime for the suspected blocking I/O and investigate the VideoToolbox, warning, and upload-state observations separately. Done means reproducing or isolating the stall cause and defining scoped fixes with tests or log evidence for the affected behaviors.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Description

bug
Description

38.5-minute recording (14:01:52 → 14:40:24 UTC). During it, the pipeline froze 16 times:

  • Video: 16 Wall-clock-confirmed forward jump events, total_forward_skew_secs="222.033" (~10% of the recording missing)
  • Mic: 6 silence insertions, total_silence_ms=64429
  • System audio: 172 silence insertions, total_silence_ms=69615, plus dropping frames due to full channel

Evidence that the whole process stalls, not just capture
The periodic memory snapshot normally fires at :25 every minute. During the stalls it fires late:

  • 14:06:32 (+6.4 s), 14:19:37 (+12 s), 14:21:42 (+16.5 s), 14:28:32 (+6.5 s)

There are also windows with no log lines at all from any thread:

  • 14:13:57.7 → 14:14:22.2 (24.5 s)
  • 14:15:57.4 → 14:16:20.1 (22.6 s)
  • 14:19:15.3 → 14:19:37.9 (22.6 s)
  • 14:21:17.9 → 14:21:42.4 (24.5 s)
  • 14:28:07.8 → 14:28:32.4 (24.6 s)

Mic and system-audio drops happen exactly in these windows: the sources keep producing data, but consumers are not draining the channels.

Suspicious pattern
The longest video gaps are almost identical: 21.33, 21.35, 21.47, 21.23, 21.44, 21.77 s. This looks like a fixed timeout somewhere rather than random I/O latency.

Hypothesis (unverified)
Blocking file I/O on the shared async runtime. If the output volume (an SD card here) has a write-latency spike, all runtime workers block, including the muxers and timers. A recorder should absorb storage hiccups with buffering instead of dropping audio.

Other observations from the same log

  • VideoToolbox zero-copy input unavailable ... scaling 4112x2658 -> 4096x2648 requires the software input path, but the encoder is then initialized at 4112×2658. These messages contradict each other, and the software path adds load for no apparent reason.
  • System audio dropping frames WARN is re-logged every 5 s even when the dropped counter does not change, producing hundreds of redundant warnings.
  • At recording start: Recording upload state could not be read; files retained error=No such file or directory (state is read before it is created).

Full log attached- cap-desktop.log

Additional Context
  • Cap version: 0.6.0
  • Operating system, version: 26.2 (25C56)
  • Device (optional): MacBook Pro M1 Pro, 16 GB RAM
Langage dominant
Rust
Étoiles
22.8k
Forks
2k
Merge moyen
10 h 44 min
PR mergées (30 j)
88

Préparer son environnement

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Autres issues de CapSoftware/Cap

Toutes les issues de CapSoftware/Cap

Issues similaires

Plus d'issues Rust

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.