Bug 249153 - Xorg with almost 100% CPU now and then during digiKam's usage
Summary: Xorg with almost 100% CPU now and then during digiKam's usage
Status: RESOLVED FIXED
Alias: None
Product: digikam
Classification: Applications
Component: Portability-Runtime (show other bugs)
Version: 1.2.0
Platform: Ubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: Digikam Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-08-26 23:22 UTC by Mathias Lindner
Modified: 2017-07-25 17:08 UTC (History)
1 user (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Mathias Lindner 2010-08-26 23:22:10 UTC
Version:           1.2.0 (using KDE 4.4.2) 
OS:                Linux

After extensive usage of digikam (moving files, tagging, rating, browsing, etc.) Xorg starts to use almost 100% CPU load for several minutes. Afterwards, everything is normal for several minutes until it starts again. During this time, digiKam is almost not responsive (but it doesn't crash).
Sometimes even my window decoration vanishes reloading Metacity with the default decoration.

I never have this behaviour without using digiKam. And it never occurs just after starting digiKam but always after some longer work. Restarting digiKam helps for some time.

I run Ubuntu 10.04 with recent updates.

I am not quite sure what else to tell you. What information do you need? How can I investigate this further?

Reproducible: Always

Steps to Reproduce:
Just run digiKam a little longer (something between one and three hours).
Comment 1 Marcel Wiesweg 2010-08-31 15:44:33 UTC
Indicative of a problem between your window manager, Xorg and your graphics driver. Don't think digikam is more than the trigger.
Comment 2 Marcel Wiesweg 2010-08-31 15:45:24 UTC
Ah yes, of course: You're running 1.2.0. Try 1.4.0, maybe I'm wrong and it's some digikam bug already fixed.
Comment 3 Mathias Lindner 2010-08-31 15:50:59 UTC
Ah, this sounds really good :) Could you please link the original bug report? I am just curious because I have not found any hint about my problem before I have files this report...

Unfortunately, Ubuntu contains only 1.2.0. I tried compiling digiKam several times and didn't really manage it. So I guess I'll stick with this behaviour for some weeks and wait for the new Ubuntu release. But waiting is much more comfortable - now that I know it will be better after an update.
Comment 4 Marcel Wiesweg 2010-09-01 16:17:23 UTC
I dont rule out it's a digikam bug, but it's more likely a xorg/driver problem - which also has a chance to be fixed after an update.
Comment 5 caulier.gilles 2011-12-13 09:44:19 UTC
Mathias,

This file still valid ?

Gilles Caulier
Comment 6 caulier.gilles 2013-11-25 13:00:33 UTC
We need feedback using digiKam 3.5.0

Gilles Caulier
Comment 7 caulier.gilles 2015-06-30 08:07:43 UTC
New digiKam 4.11.0 is available :

https://www.digikam.org/node/740

Can you reproduce the problem with this release ?
Comment 8 Mathias Lindner 2015-06-30 09:29:56 UTC
Sorry for not reporting for such a long while. Today was the first time I got a mail with your comment - just did not take any notice about your answers :\

In the meanwhile, 5 years later, I run Manjaro Linux with a recent digikam and never experienced such problems for a long while. Either you have fixed the bug sometime in between or it was no bug of digikam and vanished with changing the OS.

The only annoying several-minutes freezing time occurs during moving images from one album to another. But this is a whole other story and has nothing to do with this bug here :) I suggest we can close this.