Bug 159377 - High CPU useage while changing exif data
Summary: High CPU useage while changing exif data
Status: RESOLVED FIXED
Alias: None
Product: digikam
Classification: Applications
Component: Database-Scan (show other bugs)
Version: 0.9.2
Platform: Debian stable Linux
: NOR normal
Target Milestone: ---
Assignee: Digikam Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-03-15 22:56 UTC by Tim
Modified: 2017-07-23 20:53 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In: 5.7.0
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Tim 2008-03-15 22:56:49 UTC
Version:           0.9.2 (using KDE 3.5.8)
Installed from:    Debian stable Packages
OS:                Linux

I am running mepis 7 (a Debian stable drivative), Digikam comes from the debian etch repos. Due to bad house keeping in the past of my digital pictures I have had to re-do the exif data on several thousand pictures.

Here is the problem, open a console and start top, now open digikam, select an album of picture (around 20+ pictures should do, for the record mine are in .jpg format and around 2mb in size), select all the pictures in the album, now goto Image menu >> metadata >> edit exif data from the window that opens change the year on the "Original date" and Digitisation date" then click forward, do this to about 6 pictures then quickly click back to the console and note what taking all the processor.

On my box I find that two program starting hogging the processor sending it to 99% useage and the temperture climbing slowly until I have to stop for a break. The two programs in question are:

Kio-digikamdate (the worst offender)
Kio-digikamalbu

My box is a P4 2.8ghz with 1gb of memory which has 600mb+ of free memory while carrying out the above.
Comment 1 Tim 2008-03-15 22:57:37 UTC
This is similar to the high cpu recorded in bug 146557
Comment 2 caulier.gilles 2009-06-11 19:38:43 UTC

*** This bug has been marked as a duplicate of bug 146557 ***
Comment 3 caulier.gilles 2017-07-23 20:53:59 UTC
This problem is relevant of digiKam KIO slaves which are dropped since version 5.0.0 in favor of a multithreaded interface to query the database. It will not reproducible.