You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I like to use feh very much but one behaviour is very annoying and can even lead to a system crash. If you open a directory with feh which also contains video files (.mp4, .mkv perhaps others too) the following happens:
If the next file is a video file, it will be loaded into memory completely, no matter how big it is. feh is completely blocked during this time and cannot be terminated, nor the file can be skipped.
Since the file is loaded into memory completely, this can cause a system crash if the video is very large or the memory is low.
The console will then display the error message
feh WARNING: ... - No Imlib2 loader for that file format
I would appreciate it very much if feh would ignore videos in a future version, or at least files above a certain size.
System: Arch Linux
Version: feh 3.3-2
The text was updated successfully, but these errors were encountered:
The problem can easily be solved by the following call: find . -type f -iregex ".*\.\(jpg\|jpeg|bmp|png|pnm|tiff|gif\)$" -size -30M -print0 | xargs -0 feh
I like to use feh very much but one behaviour is very annoying and can even lead to a system crash. If you open a directory with feh which also contains video files (.mp4, .mkv perhaps others too) the following happens:
If the next file is a video file, it will be loaded into memory completely, no matter how big it is. feh is completely blocked during this time and cannot be terminated, nor the file can be skipped.
Since the file is loaded into memory completely, this can cause a system crash if the video is very large or the memory is low.
The console will then display the error message
I would appreciate it very much if feh would ignore videos in a future version, or at least files above a certain size.
System: Arch Linux
Version: feh 3.3-2
The text was updated successfully, but these errors were encountered: