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 摘要。