Bug 243915 - Digikam uses all memory and hangs when importing a directory from the hard drive with a large image
Summary: Digikam uses all memory and hangs when importing a directory from the hard dr...
Status: RESOLVED FIXED
Alias: None
Product: digikam
Classification: Applications
Component: Import-IconView (show other bugs)
Version: 1.2.0
Platform: Fedora RPMs Linux
: NOR crash
Target Milestone: ---
Assignee: Digikam Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-07-08 06:38 UTC by Andrew McNabb
Modified: 2017-08-16 21:54 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In: 5.1.0


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Andrew McNabb 2010-07-08 06:38:47 UTC
Version:           1.2.0 (using KDE 4.4.4) 
OS:                Linux

I upgraded to Fedora 13 and tried to load my pictures directory into digikam.  My system has 2 GB of RAM, and Digikam used quite a bit of memory when importing the images.  When it got to a subdirectory with a large image (a 16384x8192 pixel TIFF), the memory usage went even higher, and the system nearly froze due to swap thrashing until I killed Digikam.  I then moved out the subdirectory with the large image and restarted Digikam, and this time it loaded without hanging.

Reproducible: Always
Comment 1 caulier.gilles 2010-11-24 09:10:21 UTC
digiKam 1.6.0 is out:

http://www.digikam.org/drupal/node/550

Please update and check if this entry still valid.

Thanks in advance

Gilles Caulier
Comment 2 Marcel Wiesweg 2011-01-18 14:46:24 UTC
Did you try to edit/view the image, or do you refer to the initial scan when digikam sees the picture for the first time?

In the first case: Yes, an 8bit image of this size will use 512 MB of memory. Dont expect that to change in the near future.
In the latter case: Then I assume this has been fixed in libexiv2, which used to allocate lots of memory for large TIFFs in older versions.
Comment 3 Andrew McNabb 2011-01-18 17:43:41 UTC
This problem occurred during the initial scan.  I have not recently retested this problem, but I'll try to get to it soon.
Comment 4 caulier.gilles 2011-07-06 10:54:26 UTC
We need feedback using a recent version. 2.0.0 RC is out, please test...

Thanks in advance

Gilles Caulier
Comment 5 caulier.gilles 2015-07-03 05:58:32 UTC
New digiKam 4.11.0 is available.

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

Can you reproduce the problem with this release ?

Gilles Caulier
Comment 6 caulier.gilles 2016-07-15 16:10:15 UTC
With digiKam 5.0.0, this problem is not reproducible.
I close this file now. Don't hesitate to re-open if necessary.
Gilles Caulier