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

[MacOS] Recovery fails with IO error: File exists (os error 17) and cannot be retried

Ouverte
  • Quelque chose ne va pas ?
#2,386 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é
4/5
Temps estimé
3-5 jours
Accessibilité débutants
45/100
Type d'issue
Bug
Clarté
Plutôt claire
Activité
Active
Stack technique
macos, rust
Domaine
desktop, operating-systems

Piste de recherche

Start with the attached debug log and trace the desktop recovery flow after fragmented segments are found, focusing on the finalization step that reports OS error 17. Reproduce the failure on macOS, identify the conflicting file-handling condition, and verify that recovery succeeds or reports a meaningful error without deleting the original recording.

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

Description

bug
Description

After a recording unexpectedly enters the recovery state, attempting to recover it consistently fails with:
IO error: File exists (os error 17)

The error is reproducible on every recovery attempt. Restarting the recovery process does not help, and the recording remains unrecoverable through the UI.

The debug log shows that the recording pipeline finishes successfully, but finalization fails afterward:

Found 1 fragmented segments in "...cap" with estimated duration 0ns
Failed to finalize fragmented recording: Failed to finalize recording: IO error: File exists (os error 17)

This appears to be an internal file-handling or finalization issue. The recovery process may be attempting to create a file that already exists, but the exact conflicting path is unclear.

Expected behavior:
  • Recovery should successfully finalize the recording, or provide a meaningful error identifying the underlying problem.
  • Repeated recovery attempts should not get permanently stuck on the same error.
  • The original recording data should be preserved when recovery fails.
Actual behavior:
  • Recovery repeatedly fails with the same File exists error.
  • The only apparent alternative is Discard, which permanently deletes the recording.
Reproduction
  1. Record the screen for an extended period (approximately 30 minutes in my case).
  2. Let the recording finish.
  3. When Cap enters the recovery state, attempt to recover the recording.
  4. Recovery fails with IO error: File exists (os error 17).
  5. Retry recovery — the same error occurs again.
  6. The recording cannot be recovered through the UI.
Additional Context

Cap version: 0.6.0
Operating system, version: macOS 26.2 (25C56)
Device: MacBook Pro M1 Pro, 16 GB RAM

The recording was approximately 30 minutes long.

cap-desktop-2026-09-29.log

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.