[Digikam-devel] [Bug 297793] digiKam does not display preview images for pictures created with Panasonic DMC-TZ7

Torsten Enderling carfesh at gmx.net
Fri Apr 13 09:16:24 BST 2012


https://bugs.kde.org/show_bug.cgi?id=297793

--- Comment #23 from Torsten Enderling <carfesh at gmx.net> ---
Hi,

setting that large address aware flag will have no effect on a normal 32 bit
Windows, so it is safe to set it in any case, it just will not improve the
situation. On a 64 bit system this will allow 4 GB of maximum virtual memory
usage (please note that this is not physical memory used, but virtual memory
that may be swapped out to the hard disk); on a 32 bit system it depends,
normally you will have 2GB available, and only if /3GB is set in the boot.ini
this will give the process 3GB. So the flag will not harm other users.

But I think the real question is: does digiKam really need more than 2GB of
memory to function? I can see the virtual memory going up quickly during the
launch of digiKam (in the splash screen), but the physicial usage remains quite
constant; my guess is that something (just as an example let's say the loading
of the KIPI plugins) is doing a lot of work during intialization, consuming
memory, but not freeing the memory properly on Windows. Once it is started up
completely, the number remains quite constant. Few applications use that much
memory constantly - an example from my system is a SQL server, VMware
Workstation and obviously games. But ACDSee and Lightroom as an example manage
to deal with around 512MB-1024MB virtual memory when I start them.

I think setting that large address aware flag should only serve as a workaround
until it can be found out why digiKam needs so much memory - I am happy for now
because I can start actually using digiKam for work, however it would be bad if
in 4 weeks I managed to reach the 4GB limit :)

I will play around with digiKam to see if I find some setting that has an
effect on that number so that maybe the area can be narrowed down; for example
I just disabled the scan for new files on startup, but that didn't improve the
memory use.

Kind regards,
  Torsten

-- 
You are receiving this mail because:
You are the assignee for the bug.



More information about the Digikam-devel mailing list