Tools->Maintainance->Rebuild Thumbnails (scan changed) generates large memory leak.
Fedora 19 Gnome, X86_64 w/ 12GB Memory, AMD quad core, MySQL database on local machine.
Yum installed from Fedora 19 repository - digikam 3.5.0
Memory goes from a few GB linearly up to 11GB during the scan for changed/new thumbnails.
Submitted to the KDE bug tracking system as digikam bug 326525, but the problem seems to be in the libPGF library which is built as external shared in the Fedora distro. This does not happen with the libPGF provided in the digikam core source.
Steps to Reproduce:
1.Select Maintainance->Rebuild thumbnails->scan for new
2. Watch the memory usage climb until you run out.
Memory climbs linearly up to max available on the machine (12 GB)
Memory should be stable
I can't build thumbnails until this is fixed.
Last released libpgf 6.12.24. Trying 6.12.27 from svn.
libpgf-6.12.27-0.1.svn119.fc19 has been submitted as an update for Fedora 19.
libpgf-6.12.27-0.1.svn119.fc18 has been submitted as an update for Fedora 18.
libpgf-6.12.27-0.1.svn119.fc20 has been submitted as an update for Fedora 20.
Can you please test libpgf-6.12.27-0.1.svn119.fc19
If it don't fixes bug I will try to build libpgf with -DLIBPGF_DISABLE_OPENMP.
* should fix your issue,
* was pushed to the Fedora 20 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing libpgf-6.12.27-0.1.svn119.fc20'
as soon as you are able to.
Please go to the following url:
then log in and leave karma (feedback).
Please test libpgf-6.12.27-0.2.svn119.fc19 built with -DLIBPGF_DISABLE_OPENMP
libpgf-6.13.45-0.1.svn123.fc20 has been pushed to the Fedora 20 stable repository. If problems still persist, please make note of it in this bug report.
libpgf-6.13.45-0.1.svn123.fc18 has been pushed to the Fedora 18 stable repository. If problems still persist, please make note of it in this bug report.
libpgf-6.13.45-0.1.svn123.fc19 has been pushed to the Fedora 19 stable repository. If problems still persist, please make note of it in this bug report.