Hacktoberfest 2026: die Issues, die Maintainer für den Oktober markiert haben – offen und einsteigerfreundlich. Hacktoberfest-Issues durchsuchen

Cap启动崩溃反馈官方

Offen
  • Stimmt etwas nicht?
#2,403 1 Kommentar 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Maintainer antworten meist innerhalb von 1 Tag

Dieses Issue hat noch niemand übernommen.

Bewertung

Schwierigkeit
4/5
Geschätzter Aufwand
3-5 Tage
Anfängerfreundlichkeit
38/100
Issue-Typ
Bug
Klarheit
Muss geklärt werden
Aktivitätsstatus
Aktiv
Tech-Stack
rust
Bereich
computer-graphics, desktop, operating-systems

Rechercherichtung

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.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

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.）

Vorherrschende Sprache
Rust
Sterne
23.4k
Forks
2.1k
Ø Merge
1 T. 18 Std.
Gemergte PRs (30 T.)
252

Entwicklungsumgebung

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus CapSoftware/Cap

Alle Issues in CapSoftware/Cap

Ähnliche Issues

Weitere Issues zu Rust

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.