hydrus icon indicating copy to clipboard operation
hydrus copied to clipboard

Crash when opening second video under certain circumstances

Open mmaker-gh opened this issue 1 year ago • 3 comments

Hydrus version

v575

Qt major version

Qt 6

Operating system

Other (aka none of the above, specify in the comments)

Install method

Third party (AUR, Docker, Chocolatey, etc. Specify in comments)

Install and OS comments

Docker

Bug description and reproduction

I've recently migrated my install from Windows 11 to Docker, and this is the only noticeable issue I've came across. The type of crash that occurs (soft crash that reloads client vs. hard crash that hangs client and prevents reload) also seems to depend on the order of events. I'm unfortunately having trouble reproducing the hard crash so I'm only making note of the soft crash for now.

Soft crash

  1. Click thumbnail of a video file in the gallery
  2. Click thumbnail of a different video file in the gallery
  3. Crash
Video reproduction

https://github.com/hydrusnetwork/hydrus/assets/133693431/7828a0bf-015c-4357-afd1-ae82118833f7

Note that the video choice here does not seem to be relevant. The same crash occurs if the thumbnail selection is reversed.

https://github.com/hydrusnetwork/hydrus/assets/133693431/e21c1023-f917-4d8c-8c98-df2ff9344bfa

Log output

----------
SOFT CRASH
----------
v575, 2024-05-20 16:35:55: [MPV error] vo/gpu/drm: Can't open TTY for VT control: No such device or address
v575, 2024-05-20 16:35:55: [MPV error] vo/gpu/drm: Listing DRM devices with drmGetDevices failed! (No such file or directory)
v575, 2024-05-20 16:35:55: [MPV error] vo/gpu/drm: Failed to find a usable DRM primary node!
v575, 2024-05-20 16:35:55: [MPV error] vo/gpu-next/drm: Can't open TTY for VT control: No such device or address
v575, 2024-05-20 16:35:55: [MPV error] vo/gpu-next/drm: Listing DRM devices with drmGetDevices failed! (No such file or directory)
v575, 2024-05-20 16:35:55: [MPV error] vo/gpu-next/drm: Failed to find a usable DRM primary node!
v575, 2024-05-20 16:35:55: [MPV error] vo/xv: No Xvideo support found.
v575, 2024-05-20 16:35:55: [MPV error] vo/vaapi/vaapi: libva: vaGetDriverNames() failed with unknown libva error
v575, 2024-05-20 16:35:55: [MPV error] vo/vaapi/vaapi: Failed to initialize VAAPI: unknown libva error
v575, 2024-05-20 16:35:55: [MPV error] ao/alsa: Playback open error: No such file or directory
v575, 2024-05-20 16:35:55: [MPV fatal] ao/jack: cannot open server
v575, 2024-05-20 16:35:55: [MPV error] ao/sndio: Can't open audio device default.
v575, 2024-05-20 16:35:55: [MPV error] ao: Failed to initialize audio driver 'sndio'
v575, 2024-05-20 16:35:55: [MPV error] cplayer: Could not open/initialize audio device -> no sound.
v575, 2024-05-20 16:35:59: [MPV error] vo/gpu/drm: Can't open TTY for VT control: No such device or address
v575, 2024-05-20 16:35:59: [MPV error] vo/gpu/drm: Listing DRM devices with drmGetDevices failed! (No such file or directory)
v575, 2024-05-20 16:35:59: [MPV error] vo/gpu/drm: Failed to find a usable DRM primary node!

mmaker-gh avatar May 20 '24 16:05 mmaker-gh

Using MPV in the docker container likely just won't work very well. You should probably switch it to the "show open in external button" option for videos and animations and use something like Hydrus Web for viewing media.

floogulinc avatar May 20 '24 17:05 floogulinc

Thanks, that does prevent the crash which was actually my primary concern. I am already using Hydrus Web to view media otherwise (thanks for that too) -- this really only comes up for me when I have to access the container to manage subscriptions or clean up files, but that workaround will do for now.

mmaker-gh avatar May 20 '24 17:05 mmaker-gh

I had this problem when the version of the mpv library was too out of sync with the qt library. Welcome to dependancy hell, please ensure your .so and .dlls are correctly stowed.

bbappserver avatar Sep 08 '24 13:09 bbappserver