Hacktoberfest 2026:維護者為十月標記出來的 issue,仍然開放、適合新手。 瀏覽 Hacktoberfest issue

Cap启动崩溃反馈官方

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

維護者通常 1 天內回覆

還沒有人認領這個 Issue。

評估

難度
4/5
預估耗時
3-5 天
新手友好度
38/100
Issue 類型
缺陷
描述清晰度
需要釐清
活躍度
活躍
技術堆疊
rust

研究方向

Start with the reported logs at %LOCALAPPDATA%\so.cap.desktop\logs\cap-desktop-errors.log and cap-desktop.log, focusing on the cap_desktop_lib GPU recovery path and cap_rendering DisplayLayer initialization. Reproduce on the described Windows 10 dual-GPU, multi-monitor setup and investigate the DXGI Desktop Duplication area. Done means the app remains open in both hardware and software-rendering recovery paths without silently exiting.

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

描述

bug

Cap Desktop 启动即崩溃 Bug 报告

提交到: https://github.com/CapSoftware/Cap/issues (New Issue)


Title(建议标题)

Cap Desktop 0.6.0 crashes/exits silently on launch on Windows 10 (dual-GPU, multi-monitor), in both hardware and software-rendering recovery modes

Environment

  • App: Cap Desktop 0.6.0 (Windows x64, DCH)
  • OS: Windows 10 22H2 (build 10.0.19045)
  • GPU: NVIDIA GeForce RTX 2060 SUPER (driver 616.92, 2026-09) + Intel UHD Graphics 770 (hybrid dual GPU)
  • Displays: two monitors — 2560x1440 (NVIDIA) and 1920x1080 (Intel)
  • Note: machine previously also had 2 virtual display adapters installed (OrayIddDriver/向日葵, MuMu Virtual Display); disabling them did NOT change the behavior.

Symptom

  • Cap launches, window appears briefly, desktop flashes once, then the process exits silently.
  • No Windows crash report / no WER dump / no error dialog is produced.
  • Occurs every launch, reproducibly.

Log evidence (%LOCALAPPDATA%\so.cap.desktop\logs\cap-desktop-errors.log)

  1. Hardware GPU path crashes during GPU initialisation:
ERROR cap_desktop_lib::crash_sentinel: Previous Cap session terminated without a clean shutdown
 prev_pid=... prev_gpu_init_phase=true prev_graphics_recovery=false
WARN cap_desktop_lib: Previous Cap session terminated during GPU initialisation; using Windows software graphics recovery mode for this launch
  1. Software-recovery path gets further but still exits silently right after the display layer initialises (cap-desktop.log):
INFO cap_desktop_lib::gpu_context: Using software adapter for shared context (CPU rendering)
INFO cap_rendering::yuv_converter: Shared YUV converter pipelines created successfully
INFO cap_rendering::layers::display: DisplayLayer initialized with CPU YUV conversion preference
<--- process exits here, no further log, no crash sentinel entry, no WER report --->

Troubleshooting already tried (all failed)

  1. Disabled the 2 virtual display adapters (OrayIddDriver / MuMu) — no change.
  2. Updated NVIDIA driver from 536.99 → 616.92 and rebooted — no change (hardware-GPU init now succeeds, but app still exits silently after DisplayLayer init).
  3. Ran Cap as administrator — no change.
  4. The crash is not a graphics-driver TDR — no nvlddmkm / display-driver events in System log.

Expected vs actual

  • Expected: Cap opens to the main window and stays open.
  • Actual: exits silently every time, on a supported Windows 10 + NVIDIA RTX 20-series configuration, with dual-GPU/multi-monitor.

Suspected area

Likely in the display-capture / DisplayLayer / DXGI Desktop Duplication path on multi-adapter (hybrid GPU) Windows 10 setups. Happy to provide full logs / run a debug build if helpful.


(如需英文补充:This report was auto-gathered from local logs. Contact available for more details.)

主要語言
Rust
星號
23.7k
分支
2.1k
平均合併
1 天 2 小時
30 天內合併 PR
705

環境準備

  • 提供 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 摘要。