search

Stremio / stremio-bugs

🐛 Post bug reports in Issues here
67 stars 10 forks source link

Linux Wayland: Desktop app crashing after a few seconds of playing media #713

Closed lautarograc closed 6 months ago

lautarograc commented 6 months ago

Describe the bug When I play video, it crashes after 15-30secs. This is what's being logged:

[ao/pulse] starting AO
AV: 00:04:09 / 01:18:52 (5%) A-V:  0.000 Cache: 10s/4MB
[cplayer] Set property: sub-pos="98" -> 1
AV: 00:04:12 / 01:18:52 (5%) A-V:  0.000 Cache: 10s/4MB
[cplayer] Set property: sub-pos="83" -> 1
qt.qpa.wayland: Wayland does not support QWindow::requestActivate()

[libmpv_render] Window size: 1920x1080 (Borders: l=0 t=0 r=0 b=0)
[libmpv_render] Video source: 1920x1080 (1:1)
[libmpv_render] Video display: (0, 0) 1920x1080 -> (0, 0) 1920x1080
[libmpv_render] Video scale: 1.000000/1.000000
[libmpv_render] OSD borders: l=0 t=0 r=0 b=0
[libmpv_render] Video borders: l=0 t=0 r=0 b=0
AV: 00:04:15 / 01:18:52 (5%) A-V:  0.000 Cache: 10s/3MB
[libmpv_render] Window size: 1600x941 (Borders: l=0 t=0 r=0 b=0)
[libmpv_render] Video source: 1920x1080 (1:1)
[libmpv_render] Video display: (0, 0) 1920x1080 -> (0, 20) 1600x900
[libmpv_render] Video scale: 0.833333/0.833333
[libmpv_render] OSD borders: l=0 t=20 r=0 b=21
[libmpv_render] Video borders: l=0 t=20 r=0 b=21
AV: 00:04:16 / 01:18:52 (5%) A-V:  0.000 Cache: 10s/3MB
[libmpv_render] Window size: 1920x963 (Borders: l=0 t=0 r=0 b=0)
[libmpv_render] Video source: 1920x1080 (1:1)
[libmpv_render] Video display: (0, 0) 1920x1080 -> (104, 0) 1712x963
[libmpv_render] Video scale: 0.891667/0.891667
[libmpv_render] OSD borders: l=104 t=0 r=104 b=0
[libmpv_render] Video borders: l=104 t=0 r=104 b=0
qt.qpa.wayland: Wayland does not support QWindow::requestActivate()

[libmpv_render] Window size: 1920x1080 (Borders: l=0 t=0 r=0 b=0)
[libmpv_render] Video source: 1920x1080 (1:1)
[libmpv_render] Video display: (0, 0) 1920x1080 -> (0, 0) 1920x1080
[libmpv_render] Video scale: 1.000000/1.000000
[libmpv_render] OSD borders: l=0 t=0 r=0 b=0
[libmpv_render] Video borders: l=0 t=0 r=0 b=0
AV: 00:04:21 / 01:18:52 (6%) A-V:  0.000 Dropped: 3 Cache: 10s/3MB
[cplayer] Set property: sub-pos="98" -> 1
corrupted size vs. prev_size in fastbins Dropped: 3 Cache: 10s/3MB
Aborted (core dumped)

To Reproduce Steps to reproduce the behavior:

  1. Play some media on native player
  2. Wait for the crash

Expected behavior I expect to not have Stremio crash Screenshots If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

Additional context Add any other context about the problem here. Additional logs:

[libmpv_render] GL_VERSION='4.6 (Compatibility Profile) Mesa 22.3.0-devel'
[libmpv_render] Detected desktop OpenGL 4.6.
[libmpv_render] GL_VENDOR='AMD'
[libmpv_render] GL_RENDERER='AMD Radeon RX 6800 XT (navi21, LLVM 15.0.3, DRM 3.54, 6.5.0-25-generic)'
[libmpv_render] GL_SHADING_LANGUAGE_VERSION='4.60'
[libmpv_render] Loaded extension GL_NV_vdpau_interop.
[libmpv_render] GL_*_swap_control extension missing.
[libmpv_render] Testing FBO format rgba16f
[libmpv_render] Using FBO format rgba16f.
[libmpv_render] No advanced processing required. Enabling dumb mode.
[libmpv_render] Loading hwdec driver 'vaapi-egl'
[libmpv_render/vaapi-egl] using VAAPI EGL interop
[libmpv_render/vaapi-egl] Trying to open a x11 VA display...
[libmpv_render/vaapi-egl] Trying to open a wayland VA display...
[libmpv_render/vaapi-egl] Trying to open a drm VA display...
[libmpv_render/vaapi-egl] Could not create a VA display.
[libmpv_render] Loading failed.
[libmpv_render] Loading hwdec driver 'cuda-nvdec'
[libmpv_render/cuda-nvdec] cu->cuInit(0) failed -> CUDA_ERROR_NO_DEVICE: no CUDA-capable device is detected
[libmpv_render] Loading failed.
[libmpv_render] Loading hwdec driver 'drmprime-drm'
[libmpv_render/drmprime-drm] Failed to retrieve DRM fd from native display.
[libmpv_render] Loading failed.

edit: important information, the crashes started to happen after I switched from X11 to Wayland. No other issues experienced otherwise

TRtomasz commented 6 months ago

This kind of esoteric issue wont be fixed and in 99% cant be fixed by us. Maybe it is the same as here so you can try this workaround https://github.com/githubuser0xFFFF/Qt-Advanced-Docking-System/issues/288