Hacktoberfest 2026 : les issues que les mainteneurs ont marquées pour octobre, ouvertes et accessibles aux débutants. Parcourir les issues Hacktoberfest

Cap启动崩溃反馈官方

Ouverte
  • Quelque chose ne va pas ?
#2,403 1 commentaire 0 réactions 0 personnes assignées Voir sur GitHub

Les mainteneurs répondent en général sous 1 jour

Personne n'a encore pris cette issue.

Évaluation

Difficulté
4/5
Temps estimé
3-5 jours
Accessibilité débutants
38/100
Type d'issue
Bug
Clarté
À clarifier
Activité
Active
Stack technique
rust
Domaine
computer-graphics, desktop, operating-systems

Piste de recherche

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.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Description

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

Langage dominant
Rust
Étoiles
23.4k
Forks
2.1k
Merge moyen
2 j 4 h
PR mergées (30 j)
289

Préparer son environnement

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Autres issues de CapSoftware/Cap

Toutes les issues de CapSoftware/Cap

Issues similaires

Plus d'issues Rust

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.