0.5.6: silent crash during recording on Windows 11 (0xc0000005, mostly ntdll.dll) - recording lost, no error shown

Open
#2,019 2 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Quiet
Tech stack
rust, tauri

Research direction

Start by reproducing the crash when pausing a screen-and-mic recording on Windows 11, then inspect the Cap logs and Windows Event Log entries for the access violation. Done means recording no longer exits silently, the recording is finalized with project-config.json, and an error is surfaced if shutdown fails.

Written by the indexing model from the issue text.

Description

Summary

Since updating to 0.5.6 (released Jul 17), Cap crashes silently mid-recording on Windows 11. The recording indicator/tray simply disappears, no error dialog is shown, and the recording is lost (the .cap folder is left without project-config.json, only orphaned DASH segments). Before 0.5.6 the same setup was stable for weeks of daily recordings.

What triggers it
  • Most reliably: pressing Pause during a recording (reproduced several times).
  • But it also dies spontaneously during recording with no interaction at all — we only noticed because the recording indicator was gone.
Windows Event Log evidence

7 APPCRASH events on Jul 18 alone, all Cap.exe 0.5.6.0 (timestamp 0x6a4edb0e), exception code 0xc0000005 (access violation):

Time (local) Faulting module Offset
10:04 ntdll.dll 10.0.26100.8521 0x21dc9
10:33 ntdll.dll 0x21dc9
10:37 ntdll.dll 0x21dc9
10:40 ntdll.dll 0x164747
11:22 Cap.exe 0x1e9ba80
11:28 ntdll.dll 0x1decd
11:32 ntdll.dll 0x164747

Cap's own logs end abruptly mid-recording (no "pipeline shutdown" / teardown lines), consistent with a hard process crash. The ntdll offsets (heap paths) at multiple distinct addresses suggest heap corruption rather than a single bad call site.

Environment
  • Cap 0.5.6.0 (desktop, installed via .exe), path C:\Users\<user>\AppData\Local\Cap\Cap.exe
  • Windows 11 Home, build 26200
  • Recording: screen + mic, DASH segments visible in %APPDATA%\so.cap.desktop\recordings\
Additional note

Older releases on GitHub currently have no installer assets attached, so downgrading as a workaround isn't possible. If you could attach a 0.5.5 (or last-known-good) Windows installer to a release, that would help affected users a lot while this is investigated.

Happy to provide full logs or the WER report IDs if useful.

Dominant language
Rust
Stars
25k
Forks
2.4k
Avg merge
1d 8h
Merged PRs (30d)
676

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from CapSoftware/Cap

All issues in CapSoftware/Cap

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.