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

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

--- Comment #20 from Torsten Enderling <[hidden email]> ---
Interesting - since I've done that in the past for games that do not utilize
the full memory, I've applied CFF Explorer's 4GB path to digiKam and voila -
for now it works, the virtual size of digiKam is around 2GB now in Process
Explorer and I can open images without that malloc failure.

So I'm convinced it's related to the 2GB virtual address space limit that 32
bit application have on Windows.

CFF Explorer can be found here: http://www.ntcore.com/exsuite.php

--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

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

--- Comment #21 from Torsten Enderling <[hidden email]> ---
A nice explanation of those limits can be found in the wikipedia:
https://en.wikipedia.org/wiki/Virtual_address_space.

digiKam is using the 2GB up on my system, making it large address aware
increases that limit to 4GB.

--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Gilles Caulier-4]

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

--- Comment #22 from Gilles Caulier <[hidden email]> ---
This wantmean that digiKam under windows can be only used on 64 bits ?

Gilles Caulier

--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

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

--- Comment #23 from Torsten Enderling <[hidden email]> ---
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.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

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

--- Comment #24 from Torsten Enderling <[hidden email]> ---
Hi,

so I have played around some more and I'm afraid the problem seems to be
related mostly to the number of images in the database, so there's no way for
me to influence it except to keep my collections small.

I have observed the behaviour a bit today more, the biggest chunk of memory is
allocated while the splash screen shows that the database is being loaded.

I have created some test databases; I have one with around 12.000 images - when
I open my large address aware patched digiKam with that database, virtual
memory consumption is already around 3,8 GBs right after I start digiKam
(without having done any real work - just opening it is enough to use up that
memory).

So I'm afraid for large image collections, digiKam right now is not practical.
A 32 bit Windows process can never consume more than 4GB of virtual memory, the
only way around that limitation is to compile a native 64 bit application. I'm
sure there are other things on the top of your priority list.

It would be nice if you could investigate why digiKam allocates that much
memory. As mentioned, I suspect some kind of memory leak - but maybe that's
really just the way digiKam utilizes memory, I don't know what kind of
information about the images you are trying to keep in memory.

For now I'm afraid I have to keep using ACDSee, as I have some collections that
are even larger. It's too bad, because I was really amazed when I found at what
huge feature set digiKam has; I really would love to begin using it.

Kind regards,
  Torsten

--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

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

Torsten Enderling <[hidden email]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Severity|normal                      |crash

--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

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

--- Comment #25 from Torsten Enderling <[hidden email]> ---
The memory problem does not exist in build 2.3.0 for Windows; sadly there's no
2.4 build to narrow it down any further, but it may very well be that the
problem was introduced with a new feature or change in the newer versions; I'm
not sure what that could be.

--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Gilles Caulier-4]

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

--- Comment #26 from Gilles Caulier <[hidden email]> ---
Official digiKam 2.6.0 release is out since few days now :

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

Please, check if this entry still valid, or update report accordingly.

Thanks in advance.

Gilles Caulier

--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

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

--- Comment #27 from Torsten Enderling <[hidden email]> ---
Hi,

I wanted to verify if this issue still exists. However I cannot start digiKam
2.7.0; I experience the issue described under
https://bugs.kde.org/show_bug.cgi?id=305191

Kind regards,
  Torsten

--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

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

--- Comment #28 from Torsten Enderling <[hidden email]> ---
Ok, so after removing an attached USB stick I can start digiKam. The issue
still exists in 2.7 - once virtual memory allocation reaches 1,8GB, the GUI
will start behaving eratically.

Oddly enough, no alloc error messages are shown in debugview anymore, but it is
still unusable.

--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

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

Torsten Enderling <[hidden email]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
            Summary|digiKam does not display    |digiKam for Windows
                   |preview images for pictures |consumes large amounts of
                   |created with Panasonic      |virtual memory leading to
                   |DMC-TZ7                     |malloc failure

--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Ananta Palani]

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

--- Comment #29 from Ananta Palani <[hidden email]> ---
Git commit 57b269e2d6dfd8f0c11d482ec12d3e9c126c1cd1 by Ananta Palani.
Committed on 03/02/2013 at 23:04.
Pushed by palani into branch 'master'.

Fix thumbnails not shown in Windows and excessive use of virtual memory /
handles which may cause crashes and other unexpected behavior by removing file
monitoring and only monitoring directories for changes. These problems might
still occur with very large numbers of folders but could not be confirmed.
However, medium to large collections should no longer cause a problem.
Related: bug 290962, bug 308310, bug 310252, bug 310865, bug 312422, bug
312999, bug 291917, bug 295445, bug 297686
FIXED-IN: 3.0.0

M  +9    -2    digikam/album/albumwatch.cpp

http://commits.kde.org/digikam/57b269e2d6dfd8f0c11d482ec12d3e9c126c1cd1

--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Ananta Palani]

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

--- Comment #30 from Ananta Palani <[hidden email]> ---
I have made a beta compilation of digiKam 3.0.0 for you to test whether the
commit I just made fixes your problem:

   https://docs.google.com/file/d/0B4Esh3gAgC9QcW5nS04zQWVsNGs/edit?usp=sharing

Can you give it a try and let me know how it works for you?

--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Gilles Caulier-4]

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

Gilles Caulier <[hidden email]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |RESOLVED
   Version Fixed In|                            |3.0.0
         Resolution|---                         |FIXED
      Latest Commit|                            |http://commits.kde.org/digi
                   |                            |kam/57b269e2d6dfd8f0c11d482
                   |                            |ec12d3e9c126c1cd1

--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

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

--- Comment #31 from Torsten Enderling <[hidden email]> ---
Thanks a lot, using the beta the issue I saw in my collection has disappeared,
I can browse it fine now, great job!

--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel