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
- Record the screen for an extended period (approximately 30 minutes in my case).
- Let the recording finish.