SUMMARY During face detection, Imagemagick working files are created in /tmp. On many systems, this is a tmpfs filesystem and is of limited space. The ability to specify a alternate location would add with stability in these situations. STEPS TO REPRODUCE 1. Start Digikam 2. Add many large image and movie files. 3. Start face detection OBSERVED RESULT Large files get created in /tmp which can fill small filesystems. EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Fedora 30, kdelibs-4.14.38 (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION
I can not reproduce that the ImageMagick loader in digiKam creates any files in /tmp. Linux/KDE Plasma: Fedora 30, kdelibs-4.14.38 Use you KDE4 ??? Maik
Created attachment 120314 [details] attachment-2432-0.html Hi Maik. I run under the Gnome destkop with the KDE libraries. I assume the files are created by ImageMagick as they are under names like "magick-639773V132v321lubl.pam". I think they are created when processing video files, but nothing seems to be able to top open them. They are described as " Netpbm PAM image file" by file. While typing this message, I just went back and tested again and it appears to be only .mp4 exhibit this issue. I'll see if I can try encoding some different files and see if it's related to either size, or the flavour of MP4. Rob On Sat, 2019-05-25 at 21:41 +0000, Maik Qualmann wrote: > https://bugs.kde.org/show_bug.cgi?id=407948 > > Maik Qualmann <metzpinguin@gmail.com> changed: > What |Removed |Added--------------- > ----------------------------------------------------------- > -- CC| > |metzpinguin@gmail.com > > --- Comment #1 from Maik Qualmann <metzpinguin@gmail.com> ---I can > not reproduce that the ImageMagick loader in digiKam creates any > files in/tmp. > Linux/KDE Plasma: Fedora 30, kdelibs-4.14.38Use you KDE4 ??? > Maik
The ImageMagick loader in digiKam does not process video files. The current GIT version also includes an additional check of the image mime type. I'm sure the temporary files are not created by digiKam. Maik
It's probably create by IM loader as well, especially for video files. And yes, video files can be loaded in IM through... ffmpeg using command line interface . This is weird... I tried to disabled the video support in IM but it's impossible to break completly the code. So in digiKam core we must take a care that no video files are re-routed to IM loaders. Gilles
Already done: https://invent.kde.org/kde/digikam/blob/master/core/libs/dimg/loaders/magickloader.cpp#L55 Maik
yes i seen. Gilles
New version from GIT skips movie/video files as expected. Thanks.
Ok, I close the bug. Temporary storage should sufficient exist, but a program should use it sparingly. DigiKam deletes its directories created by the export tools when quitting. I think an option to set the directory should not be needed. If necessary, reopen the bug report. Maik