Version: 0.9.2-beta3 (using KDE 3.5.7, Debian Package 4:3.5.7.dfsg.1-1 (lenny/sid)) Compiler: Target: i486-linux-gnu OS: Linux (i686) release 2.6.18-4-k7 Until 2 minutes ago, my Debian system hang under heavy load (not even switching to console was possible). What had happened? I selected 8 out of 55 pictures for mail transport (1024 pixel). As digikam had crashed in the end (no messages however), I can only guess that - instead of 8, all 55 pictures were prepared for sending (i.e. scaled down) - this process was started with highest priority thus making xmms stop and in the end even the TTY manager was overloaded. What should happen: - query "send 55 pictures by mail?" - run process with lower priority (nice)
Some further apps were closed during this process, namely Openoffice (several windows open).
apparently, only selected files were written to /tmp/kde-knoppix/kipi-sendimagesplugin-16661 looks like /tmp and thus / ran out of memory during that process... this is what made ooo and digikam crash, I guess
Hi Ralf, just wondering: does the problem also occur when openoffice is not running (I recently had some similar crashes with openoffice, where huge amount of RAM are used so that the kernel starts killing processes. So it could have also been openoffice killing digikam ... ;-) Could you try monitoring (eg. with top) the RAM used while exporting? Thanks, Arnd
Hi Arnd, Am Montag 17 September 2007 07:36 schrieb Arnd Baecker: > Could you try monitoring (eg. with top) the RAM used while exporting? While exporting I could not even switch to a console (ALT+F1) - the system was totally overloaded. Partly due to a full / and thus /tmp! Afterwards I only found those 5 files I meant to export in a tmp folder - so this is okay. Nevertheless, image conversion (also during html export) seems to be quite slow and cpu consuming... Regards Ralf
Hi Ralf, what I would be interested in, whether the problem is reproducible (in particular, without openoffice running at the same time). If you run top in a konsule, before you start sending the selected pictures and arange windows carefully, you should be able to see the output of top, even if the system is completely unresponsive. If the crash is reproducible and caused by digikam, a full backtrace will be needed to find the source of the problem (see: "If you are experiencing crashes with digiKam" on http://www.digikam.org/?q=contrib ) I can't comment on the speed as I don't use this tool... Thanks a lot in advance, Arnd
Ralf, SendImages kipi-plugins write temporary images to e-mail in a the /tmp folder (using KDE api). I suspect a free-space problem on your computer. What a "df" give on your computer ? Gilles Caulier
Ralf, The symptoms you described suggest that it was rather RAM shortage problem. I would guess that you couldn't switch to console due to extensive swapping and OpenOffice et al. were killed by the OOM killer. Make sure you set some sensible ulimit for memory, then try to reproduce. Only digiKam should get killed then. Pawel
Dear Arnd, thanks for replying. The crash is not reproducable: I tried even while running Openoffice with 5 open documents. This time, the task completes within 5 seconds or so (the CPU load goes up to 100% meanwhile). So, it must have been due to full /tmp partition. Thanks, should be set to "worksforme" or "invalid". Regards Ralf Am Dienstag 18 September 2007 17:42 schrieb Arnd Baecker: [bugs.kde.org quoted mail]
Thanks a lot for the feedback!
Work perfectly with new Send by Mail tool from digiKam core. Gilles Caulier