Version: 0.9.2-final (using KDE 3.5.6, Kubuntu (feisty) 4:3.5.6-0ubuntu14) Compiler: Target: i486-linux-gnu OS: Linux (i686) release 2.6.20-16-386 Following my latest crash report bug #143200 , it does not crash anymore, but is slow and use a lot of CPU. How to reproduce: Focus on one picture and do something like this: F2, paste (Ctrl+V), enter, [the focus change to the next picture], F2, paste, enter, rince and repeat. What happens? 100% use of CPU for the next 1 second for the first picture, after that the time seems to grow at 100% exponentially and eventually digiKam does not respond very well (since 100% of the CPU is used). From picture two, it seems like digiKam is trying to do two things at a time or more, probably updating is database, renaming and reworking the thumbnail? Some facts : -The folder where the album reside is 17136 elements with 23,7GB total size. -$ cat /proc/cpuinfo = Model name : Intel(R) Pentium(R) 4 CPU 2.60GHz -$ cat /proc/meminfo = MemTotal: 2075540 kB -In top: PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 30939 XXXX 23 0 170m 120m 31m S 0.0 6.0 1:10.25 digikam -The digiKam database is 3MB (If this is indeed the digikam3.db file in the album folder)
Some might have noticed it, this weekend are my bughunting days :-) So again, is this still valid? Alexandre, have you tried the latest digiKam version (0.9.5) and can you still confirm this behavior? Also there is another way to do mass renaming in digiKam. Judging from the steps you take in the described renaming process, you seem to paste in a predefined string and add a custom string or number to it. You can try to do this with "Batch->Rename images". Maybe the performance will be better because I think the album icon view will not be updated on every single renaming step, just in the end when everything is done. If this is not valid anymore, I will close it. Alexandre, please give me / us your feedback. Andi
I can't test this anymore. I have a newer machine now and have updated to 0.9.3 Close it.
Closing now...