moonlight-stream / moonlight-stream/moonlight-android

[Issue]: Video decoder crashed on TCL 55C6K when TV system overlay (volume/menu) appears during streaming

Open
#1,602 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug
Dominant language
C
Stars
7.1k
Forks
1.5k
PR merge metrics
No merged PRs in 30d

Description

Describe the bug

Moonlight crashes with a "Video decoder crashed" error (device incompatibility message) whenever a system-level
overlay renders on top of the video surface during streaming — this includes the TV's volume OSD, the controller's
guide/home button, or attempting to switch apps without ending the session. In most cases this requires a full power
cycle of the TV to recover; occasionally it shows the error dialog and Moonlight closes on its own.

Steps to reproduce
  1. Start any stream from Sunshine.
  2. While actively playing, trigger any of: pressing volume up/down on the TV remote, pressing the guide/home button on
    a connected gamepad, or trying to switch to another app without ending the session.
  3. The video freezes, and either the TV becomes fully unresponsive (requiring a power cycle) or Moonlight shows "Video
    decoder crashed" and closes.
Affected games

Occurs across every game tested so far. I have not yet specifically isolated whether it also occurs streaming a plain
desktop/Steam Big Picture session (happy to test this if useful).

Other Moonlight clients

PC

Moonlight adjusted settings

Yes

Moonlight adjusted settings (please complete the following information)

Tried forcing codec to H264 and to HEVC (both crash identically), adjusted bitrate between 40-70 Mbps, confirmed HDR
is disabled, updated Moonlight to the latest available version — none of these prevented the crash. The one change
that reliably prevents it: enabling the on-screen performance stats overlay

Moonlight default settings

Yes

Gamepad-related connection issue

No

Gamepad-related input issue

No

Gamepad-related streaming issue

No

Android version

Android 14

Device model

TCL 55C6K (55" Mini-LED, Google TV

Server PC OS version

Windows 11 version 25H2, 26200.9457

Server PC GeForce Experience version

AMD Adrenaline 26.8.1 AMD Windows Driver Version 32.0.21045.5002

Server PC Nvidia GPU driver version

AMD Radeon RX 6600 Driver Version 25.10.45.05-260808a-203303C-AMD-Softwa re-Adrenalin-Edition

Server PC antivirus and firewall software

Windows Defender and Windows Firewall (default)

Screenshots

No response

Relevant log output

Additional context

On-screen stats confirm the decoder as c2.mtk.hevc.decoder, confirming a MediaTek chipset. This may be related to
issue #1601 (same "Video decoder crashed" error on a TCL Smart TV Pro, also Android 14). Key finding: enabling the
on-screen stats overlay is 100% reliable at preventing the crash — tested over a 2+ hour session with repeated
volume/guide-button triggers and zero crashes. My guess is that rendering the stats forces Moonlight into a different
video rendering path (GPU-composited rather than a dedicated hardware overlay plane), which is more tolerant of
concurrent system UI overlays. Happy to help test debug builds or provide further logs.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No source file or test is identified. Start by reproducing the crash on the TCL 55C6K with volume or guide overlays, compare the behavior with and without the on-screen stats overlay, and review related issue #1601. Done means overlays no longer crash the decoder without requiring the stats overlay, with useful logs captured for validation.

Written by the indexing model from the issue text.

Assessment

Tech stack
android
Domain
audio-video-rtc, mobile-dev
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.