Hide Forgot
Description of problem: When importing a folder of photos to Digikam, the software uses too much memory and, in some cases (this depends on the number of pictures), it is terminated after having filled all the available memory. This renders the tool unusable for any reasonably-sized photo collection (with less than 10'000 photos the tool is already unusable as it requires more than 20GB of memory!). Digikam seems to work fine on other distributions. Version-Release number of selected component (if applicable): 2.2 and 2.3 from updates-testing How reproducible: The very high memory usage (more than 14GB) happens when importing any reasonably sized (3-4'000 photos) folder. With 5-6'000 photos the program uses more than 20GB of memory. Steps to Reproduce: 1. Start Digikam 2. Select Settings-> configure digikam 3. select the Collections folder 4. Click add collection 5. Select a folder with 3-4'000 pictures Actual results: After the scan of the selected directory the memory usage grows (up to 14-5GB for collections with 3-4'000 photos. Expected results: The tool should not use that much memory and it does not on other distributions. Additional info: The behavior is the same both when a MySQL and a SQLite database is used.
Is anybody caring of these bugs? Sorry to ask this, but I have had the impression that are just being ignored completely...
We care, don't worry. It's just that this is not reproducible by me at least, nor have I seen or heard any other similar reports, so it's hard. It's possible digikam upstream may have more advice, if you're willing to contact them about it, either via their mailing list: https://mail.kde.org/mailman/listinfo/digikam-users or bugtracker @ http://bugs.kde.org against component 'digikam'
I see you opened a thread upstream already, thanks! http://mail.kde.org/pipermail/digikam-users/2011-November/015104.html
Yes, I did, but it looks like a Fedora-only problem or, at least, the others cannot reproduce it. I would be quite surprised if I was the only one with this problem: mine is a pretty standard 64-bit installation of Fedora. Have you also had a look to the other problem (the one with MySQL)? Can you at least reproduce that one?
What other problem?
Bug #753401 How should we proceed with this bug? Is there anything I can do to provide you enough inputs to see what is happening?
Follow upstream's advice, attach gdm, run through valgrind, all of those things already suggested.
After some more testing I discovered that the high memory usage problem seems to be only on my home PC. The laptop, even though the Fedora installation is pretty much the same, does not have such a problem. Both of them are running KDE, both of them use the Nvidia proprietary drivers. I will be running digikam through gdb ASAP.
This message is a reminder that Fedora 16 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 16. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '16'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 16's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 16 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged to click on "Clone This Bug" and open it against that version of Fedora. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed.