Bug 149683 - Digikam pegs out CPU at 100% after a little usage
Summary: Digikam pegs out CPU at 100% after a little usage
Status: RESOLVED NOT A BUG
Alias: None
Product: digikam
Classification: Applications
Component: Preview-Image (show other bugs)
Version: unspecified
Platform: Gentoo Packages Linux
: NOR normal
Target Milestone: ---
Assignee: Digikam Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-09-09 01:53 UTC by Victor Trac
Modified: 2022-01-19 16:56 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In: 7.6.0


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Victor Trac 2007-09-09 01:53:47 UTC
Version:           0.9.2-final (using KDE KDE 3.5.7)
Installed from:    Gentoo Packages
Compiler:          gcc 4.1.2 
OS:                Linux

A some point after starting digikam and viewing/editing images in the embedded browser, digikam starts to peg out one of my CPUs.  Here's the output from strace:

select(14, [3 4 5 7 9 12 13], [], [], NULL) = 1 (in [12])
gettimeofday({1189295280, 596798}, NULL) = 0
gettimeofday({1189295280, 596823}, NULL) = 0
ioctl(3, FIONREAD, [0])                 = 0
select(14, [3 4 5 7 9 12 13], [], [], NULL) = 1 (in [12])
gettimeofday({1189295280, 596931}, NULL) = 0
gettimeofday({1189295280, 596956}, NULL) = 0
ioctl(3, FIONREAD, [0])                 = 0
select(14, [3 4 5 7 9 12 13], [], [], NULL) = 1 (in [12])
gettimeofday({1189295280, 597063}, NULL) = 0
gettimeofday({1189295280, 597089}, NULL) = 0
ioctl(3, FIONREAD, [0])                 = 0
...

That repeats indefinitely.
Comment 1 caulier.gilles 2007-09-09 09:40:45 UTC
Victor,

Which CPU type ? Preview mode (and editor) use multithreading to load pictures in background.

Are you few error messeges on the console ? digiKam crash ?

Gilles Caulier
Comment 2 Bram Schoenmakers 2007-09-09 11:50:16 UTC
Please read http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports to make this bug report more useful.
Comment 3 Bram Schoenmakers 2007-12-10 00:13:11 UTC
Not enough information, therefore closing.