Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Heavy memory hole when i try to play a 4k uhd video #15536

Open
6 tasks done
atohmdiy6 opened this issue Dec 17, 2024 · 0 comments
Open
6 tasks done

Heavy memory hole when i try to play a 4k uhd video #15536

atohmdiy6 opened this issue Dec 17, 2024 · 0 comments
Labels

Comments

@atohmdiy6
Copy link

mpv Information

mpv v0.39.0 Copyright © 2000-2024 mpv/MPlayer/mplayer2 projects
 built on Nov 30 2024 08:10:45
libplacebo version: v7.349.0
FFmpeg version: n7.1
FFmpeg library versions:
   libavcodec      61.19.100
   libavdevice     61.3.100
   libavfilter     10.4.100
   libavformat     61.7.100
   libavutil       59.39.100
   libswresample   5.3.100
   libswscale      8.3.100

Other Information

- Linux version: CachyOS 
- Kernel Version: 6.12.5
- GPU Model: AMD 6900XT
- Mesa/GPU Driver Version: Mesa 24.3.1-cachyos1.6
- Window Manager and Version: KDE Kwin 6.2.4
- Source of mpv: official cachyos repo
- Latest known working version:
- Issue started after the following happened:

Reproduction Steps

Try to play a 4k UHD / HDR video

Expected Behavior

Video is playing

Actual Behavior

When trying to play certain 4k UHD x265 video file, there is nothing showing in the mpv term and video is not playing. I check my system monitor and mpv is eating ram like crazy until my pc hang severally.
Then i need to kill mpv process.

I tried with --no-config or with hwdec disable without success. I thought it could be HDR related but 4k SDR video show the same issue. 1080p and below are playing fine. Then i realize AV1 and X265 encoded 4k uhd seems to play fine, bluray remux seems to be the issue.

Log File

output.txt

Sample Files

No response

I carefully read all instruction and confirm that I did the following:

  • I tested with the latest mpv version to validate that the issue is not already fixed.
  • I provided all required information including system and mpv version.
  • I produced the log file with the exact same set of files, parameters, and conditions used in "Reproduction Steps", with the addition of --log-file=output.txt.
  • I produced the log file while the behaviors described in "Actual Behavior" were actively observed.
  • I attached the full, untruncated log file.
  • I attached the backtrace in the case of a crash.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant