[Digikam-devel] [Bug 271841] New: digikam very slow when editing iptc data

[Nicolas Pomarede]

https://bugs.kde.org/show_bug.cgi?id=271841

           Summary: digikam very slow when editing iptc data
           Product: digikam
           Version: 1.9.0
          Platform: Mandriva RPMs
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: NOR
         Component: Metadata
        AssignedTo: digikam-devel at kde.org
        ReportedBy: npomarede at corp.free.fr


Version:           1.9.0 (using KDE 4.6.2) 
OS:                Linux

Although digikam is quite responsive most of the time, I noticed that each time
I edit some iptc metadata in an image, the program gets very slow for a few
seconds, sometimes up to 20-30 seconds. During that time, the UI is not
responding immediatly (scroll, click, ...)

(this problem is not related to 1.9 only, I noticed it since I used digikam a
few years ago).

Reproducible: Always

Steps to Reproduce:
This problem seems related to the number of pictures in the current album. It
seems each time I modify the iptc metadata of one image, all other images are
rescanned. The more images in the album, the more time it takes to get back to
normal.

For example, with a rather small 300 images album ; at start, everything is
responsive, I can scroll in the album view, thumbnails appear quickly, all is
good.

Now, I choose one image, edit iptc metadata and change "caption" for example
(the iptc element doesn't matter). Once I press OK to close the metadata
window, Digikam becomes very slow, clicking or scrolling can take many seconds
before having an effect, and I can see all images' thumbnails seem to be
reloaded (they quickly disappear/reappear one after the other).

There's no indication in the bottom progress bar that something is happenning,
but the program is really stuck.


Another frustrating experience is when selecting many images (let's say 40) and
choosing "edit iptc metadata". In that case, clicking "next" in the iptc window
to edit the next image's data can also take 5 seconds or more, as if a
background task was started each time one image is modified and slowed
everything.
While editing those 40 images data could take only a couple of minutes, it ends
up taking 10 minutes or more, mostly waiting for the UI to respond each time I
click on 'next'.


Is this a digikam problem, or the underlying QT window that tries to refresh
everything while only 1 image was modified ?

Are there some traces I could make to try to debug what part of Digikam is
creating this slowdown ?

-- 
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.