IINA Version

1.4.0 Build 158

Release Channel

Release

macOS Version

15.6.1

Steps to Reproduce

• Make sure there is a large MKV video on the local network (e.g.,Emby, video size 18GB).
• Try to play the video in fullscreen via CLI:
  /Applications/IINA.app/Contents/MacOS/iina-cli 'http://192.168.1.x:8096/emby/videos/<VIDEO_ID>/original.mkv?DeviceId=<DEVICE_ID>&MediaSourceId=<MEDIA_SOURCE_ID>&PlaySessionId=<SESSION_ID>&api_key=<API_KEY>&Static=true' --fullscreen=yes(example)
  You may also try using other HTTP servers to reproduce this issues

Expected Behavior

The video should start playing in fullscreen mode normally.

Actual Behavior

• When using --fullscreen=yes, IINA fails to start playback for large MKV files (e.g., 18GB) over the local network. The player shows a black screen and becomes unresponsive.
• Some videos that have never been played before may fail to start on the first attempt but play normally on the second attempt.
• Using --fullscreen=no allows the video to play normally.
• As long as --mpv-fullscreen=no is removed, the video plays normally, so I’m certain the issue is caused by --mpv-fullscreen=yes.
• This behavior does not occur in version 1.4.0beta1.
• Large MKV files can be reproduced 100%.
• Videos played for the first time are harder to reproduce due to the special case of first playback.

Crash Report or Process Sample

sample.txt

I think this is very important. Please take a look at this.

Logs

/Applications/IINA.app/Contents/MacOS/iina-cli 'http://192.168.1.x:8096/emby/videos/<VIDEO_ID>/original.mkv?DeviceId=<DEVICE_ID>&MediaSourceId=<MEDIA_SOURCE_ID>&PlaySessionId=<SESSION_ID>&api_key=<API_KEY>&Static=true' --mpv-fullscreen=yes(example)
There are no more logs beyond this point.

mpv.log

Sample Files

No response

How often can you reproduce the issue

everytime

Required Actions

• I tried my best to search from the existing issues (including closed issues) and didn't find duplicated issues.

Optional Actions

• I tested with the Nightly build and confirmed the issue is not fixed.
• I tested with the latest version of mpv and confirmed mpv doesn't have this issue.