[Bug]: Sometimes Sunshine freezes for ~2 minutes and crashes when disconnecting (ensure_only_display / revert loop)

Aperta
  • Qualcosa non va?
#5,870 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
48/100
Tipo di issue
Bug
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
cpp
Ambito
desktop

Direzione di ricerca

Start by tracing the Windows display-device settings revert path triggered when a Moonlight session disconnects, using the ensure_only_display option and the logged topology failure as entry points. Reproduce with a multi-monitor setup and inspect why the configured output is missing from the available path source data and why the revert API remains unavailable. Done means disconnecting reliably restores display settings without the repeated retry loop or Sunshine crash.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

Is there an existing issue for this?
  • I have searched the existing issues
Is your issue described in the documentation?
  • I have read the documentation
Is your issue present in the latest beta/pre-release?

None

Describe the Bug
Expected Behavior

When disconnecting from Moonlight (via Ctrl + Alt + Shift + Q), Sunshine should cleanly end the stream and revert monitor settings back to normal without getting stuck.

Current Behavior

Sometimes (not every single time, but intermittently), when I quit or disconnect from a session, Sunshine completely freezes.
Checking the logs, it fails to find the monitor in the topology and gets stuck in a loop repeating Info: Trying to revert applied display device settings. API is available: false every 5 seconds for roughly 2 minutes. During this freeze, Sunshine stops accepting new connections and eventually crashes before the Windows service restarts it.

Steps to Reproduce
  1. Have a multi-monitor setup on Windows 11 (in my case, 3 monitors).
  2. Configure dd_configuration_option = ensure_only_display and set an output_name in sunshine.conf.
  3. Stream a game or desktop to Moonlight.
  4. Exit using Ctrl + Alt + Shift + Q.
  5. It doesn't happen every single time, but occasionally Sunshine will fail to revert display settings and get trapped in the 2-minute loop below.
Relevant Log Output
[2026-10-07 14:09:52.737]: Error: Device {f8a543aa-0b19-548a-91c5-cb05160c105a} does not exist in the available path source data!
[2026-10-07 14:09:52.738]: Error: Failed to change topology to:
[
  [
    "{f8a543aa-0b19-548a-91c5-cb05160c105a}"
  ]
]
...
[2026-10-07 14:10:13.619]: Info: Trying to revert applied display device settings. API is available: false
[2026-10-07 14:10:18.647]: Info: Trying to revert applied display device settings. API is available: false
... (repeats every 5s for ~2 minutes)
[2026-10-07 14:11:55.902]: Info: Interrupt handler called
[2026-10-07 14:11:55.902]: Info: Unmapping UPNP ports...
[2026-10-07 14:11:55.903]: Error: Couldn't accept incoming connections: The I/O operation has been aborted because of either a thread exit or an application request
Relevant Sunshine Configuration
dd_configuration_option = ensure_only_display
output_name = {f8a543aa-0b19-548a-91c5-cb05160c105a}
System Information
  • Sunshine Version: 2026.914.233613 (Commit: 63d35f702ee9e362e43263742981836ec0710384)
  • Displays: Multi-monitor setup (Acer KG271U @ 144Hz primary, Samsung S24D300, BenQ GW2760HS)
Expected Behavior

No response

Additional Context

No response

Host Operating System

Windows

Operating System Version

Windows 11 Pro 64-bit (Build 26200)

Architecture

amd64/x86_64

Package

Windows - msi installer (recommended)

GPU Type

NVIDIA

GPU Model

RTX 2070

GPU Driver/Mesa Version

Driver: 32.0.16.1714 / 617.14

Capture Method

None

Apps
Log output
Online logs

No response

Lingua principale
C++
Stelle
43k
Fork
2.4k
Merge medio
1g 15h
PR unite (30g)
105

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di LizardByte/Sunshine

Tutte le issue di LizardByte/Sunshine

Issue simili

Altre issue su C++

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.