How are you releasing untested buggy versions for a paid software?

[StarAzure]

Description

Stopping recording causes stuck Cap silhouette and recording in unusable !

Reproduction

Simple - Just do a short 5 secs recording and see the results

Additional Context

• Cap version: 0.53
• Operating system, version: Windows 11
• Device (optional): 32 GB RAM, AMD, Lenovo Thinkpad with AMD 680M

[linear]

CAP-746

[tembo]

This looks related to a known pattern of Windows stop-recording issues:

• #1781 - Same symptoms (spinning indefinitely after stop, Windows 11, Thinkpad with 32GB RAM) - another user reported ~50% failure rate on recordings
• #1466 - Cap hanging when stopping recording on Windows 11

PR #1717 (merged April 2026) added layered timeouts to prevent UI freezes on stop: 5s for video source stop, 2s drain deadline, and 10s overall pipeline timeout. These fixes are in versions after 0.3.x, but you're on 0.53 so they should be present.

Given you have an AMD 680M iGPU, #1954 may also be relevant - it documents AMD Radeon 700M series driver crashes (atio6axx.dll) on Windows hybrid GPU systems. The workaround there is forcing Cap to use a discrete GPU if available, or setting CAP_RENDER_FORCE_SOFTWARE_ADAPTER=1 before launching to bypass the AMD driver entirely.

To help diagnose:

1. Logs should be at C:\Users\{username}\AppData\Roaming\so.cap.desktop\logs - if that folder is missing or empty, that's useful info (also reported missing in Cap desktop hangs when stopping recording both on live and studio #1466 and Spins indefinitely after recording is stopped or when trying to open recording #1781)

2. If you have recordings stuck in "processing", you can sometimes recover them manually by:

   • Opening the .cap folder for that recording (Previous Recordings > folder icon)
   • Looking in Content/Segments/segment-0 for the raw video files
   • Combining with ffmpeg: ffmpeg -i display.mp4 -i audio-input.ogg -c:v copy -map 0:v:0 -map 1:a:0 -c:a aac -b:a 192k output.mp4

The stop-recording path is in apps/desktop/src-tauri/src/recording.rs with pipeline timeouts in crates/recording/src/output_pipeline/core.rs. The intermittent nature suggests a race condition or resource contention, possibly GPU-related given the AMD hardware.

[StarAzure]

None of the above fixes this. Paid users shouldn't have to hack their way to recovering recordings. Please fix properly ASAP.

[simplyinquisitive]

not a paid user but i am facing the exact same issue on a win 11, rtx 4060 laptop on this latest update. not only this blank silhouette doesn't go away, the window recording playing in the editor behind it is either blank or a weird inverted color-esque gradient.

[StarAzure]

And more issues - spinning indefinitely for a short 1 min screen only recording. You guys seriously need to fix these issues. Also the lack of response to paid users is not acceptable.

[richiemcilroy]

Hey @StarAzure. Fix for this is live in main, will be released soon. Seemed to affect some users on Windows.

I'm not sure if you are in our Discord, or have emailed support, but this is where the vast majority of our support takes place.

GitHub issues is a good place to file bugs. But if they are fully blocking your workflow and you're a paying user, it's usually better to either DM me, email me, or create a support ticket in Discord :)

0.5.4 will be released very soon - cheers!