Critical Bug: Recording immediately stalls at 0s and self-terminates after 3–5s on v0.6.2

未關閉
#3,594 1 則留言 0 個 reaction 已指派 0 人 在 GitHub 檢視

維護者通常 1 天內回覆

還沒有人認領這個 Issue。

  • #3600 來自 @ghazy2001 —— 已關閉,未合併

評估

難度
4/5
預估耗時
3-5 天
新手友好度
38/100
Issue 類型
缺陷
描述清晰度
基本清楚
活躍度
活躍
技術堆疊
rust, tauri
領域
desktop

研究方向

Start by reproducing on v0.6.2 using any capture window mode and check whether the timer remains at 0s before recording stops after 3–5 seconds. The report says debug logs should be available under so.cap.desktop, but the reporter could not find a logs directory; request the operating system and version and any accessible logs to narrow down the failure. Done means recording continues, the timer advances, and a usable output is saved.

由索引模型根據 Issue 內容生成。

描述

bug
Description

After upgrading to v0.6.2, every recording attempt fails. The recording timer never advances past 0 seconds, and the app exits the recording state automatically after roughly 3–5 seconds without saving any output. This happens consistently on every attempt, on the same machine that worked on the previous version.

Reproduction

Steps to reproduce:

Launch Cap v0.6. 2.

Select any capture window mode.

Start recording.

Observe the timer.

The timer stays at 0s and does not advance. After 3–5 seconds the app exits the recording state on its own. No usable recording is produced.

Additional Context
  • Cap version:
  • Operating system, version:
  • Device (optional):
主要語言
Rust
星號
25k
分支
2.4k
平均合併
1 天 8 小時
30 天內合併 PR
676

環境準備

  • 提供 Dockerfile 或 Docker Compose 檔案
  • 沒有 Pull Request 範本
  • 閱讀貢獻指南

從這裡開始

  1. 先讀完整個 Issue,再讀專案的貢獻指南。
  2. 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
  3. Fork 儲存庫,在一個分支上完成修改。
  4. 送出 Pull Request,並在描述裡引用這個 Issue 編號。

CapSoftware/Cap 的其他 Issue

查看 CapSoftware/Cap 的全部 Issue

相似的 Issue

更多 Rust Issue

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。