Summary: | Digikam uses all memory and hangs when importing a directory from the hard drive with a large image | ||
---|---|---|---|
Product: | [Applications] digikam | Reporter: | Andrew McNabb <amcnabb> |
Component: | Import-IconView | Assignee: | Digikam Developers <digikam-bugs-null> |
Status: | RESOLVED FIXED | ||
Severity: | crash | CC: | caulier.gilles |
Priority: | NOR | ||
Version: | 1.2.0 | ||
Target Milestone: | --- | ||
Platform: | Fedora RPMs | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | 5.1.0 | |
Sentry Crash Report: |
Description
Andrew McNabb
2010-07-08 06:38:47 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 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. This problem occurred during the initial scan. I have not recently retested this problem, but I'll try to get to it soon. We need feedback using a recent version. 2.0.0 RC is out, please test... Thanks in advance Gilles Caulier New digiKam 4.11.0 is available. https://www.digikam.org/node/740 Can you reproduce the problem with this release ? Gilles Caulier 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 |