[Digikam-devel] [digikam] [Bug 309058] The digiKam database can't be synchronized with XMP sidecars.

Kevin Dalley kevin at kelphead.org
Thu Dec 12 06:06:09 GMT 2013


--- Comment #22 from Kevin Dalley <kevin at kelphead.org> ---
I performed some additional tests, changing the tag name for a tag which
had over 1000 images. Then I changed it back again.

During the change back, I hit a deadlock, at least that is my best
guess. I'm investigating it now, attaching gdb to the running process.
Digikam hung up. I did try performing other operations while the writing
was finishing.

I suspect that writing that many images tickled a bug which had existed

In addition to the deadlock, the intial change was slow, perhaps 5
minutes. Performing other operations was slow, but they did complete.

On 12/09/2013 02:49 PM, Gilles Caulier wrote:
> https://bugs.kde.org/show_bug.cgi?id=309058
> --- Comment #20 from Gilles Caulier <caulier.gilles at gmail.com> ---
> Hi Kevin,
> What's happen if a lots of images relevant of tags hierarchy changes
> needs to be updated ? This can take a while to process. To update
> files as well can decrease digiKAm performance a lots until files
> update is done. Do you tried in production ?
> I know that Aperture or Lightroom put all changes in a list to play
> when users can do it (for ex when he don't use application in
> workflow). This is the goal of Maintenance tool in digiKam. End users
> run it at the most adapted moment...
> Best
> Gilles Caulier

You are receiving this mail because:
You are the assignee for the bug.

More information about the Digikam-devel mailing list