memory consume

classic Classic list List threaded Threaded
5 messages Options
Reply | Threaded
Open this post in threaded view
|

memory consume

Martin Ehmke
Hi,

I am running digikam 0.8.0 and just noticed that it consumes so much memory,
when downloading pictures from the camera (I use USB PTP). At the beginnig
everything is fine, but the further it advances downloading the pictures, the
more memory it consumes. At the end I usually have to restart digikam, so
that my system works again...
This problem appears to exist only when/after downloading pictures.

Maybe someone knows possible reasons for that...

Best regards
Martin Ehmke
_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users
Reply | Threaded
Open this post in threaded view
|

Re: memory consume

Gilles Caulier
Le Mardi 10 Janvier 2006 11:24, Martin Ehmke a écrit :

> Hi,
>
> I am running digikam 0.8.0 and just noticed that it consumes so much
> memory, when downloading pictures from the camera (I use USB PTP). At the
> beginnig everything is fine, but the further it advances downloading the
> pictures, the more memory it consumes. At the end I usually have to restart
> digikam, so that my system works again...
> This problem appears to exist only when/after downloading pictures.
>
> Maybe someone knows possible reasons for that...
>
> Best regards
> Martin Ehmke

The better way to check memory leak is to use valgrind tool like this :

valgrind --tool=memcheck --leak-check=full --error-limit=no digikam

note that digikam must be compiled using all debug information to get witch
source code line(s) are in default.

I had no PTP camera, only USB mass storage here to test.

When you run digikam under valgrind, the speed is very low ( divide per 15
approximativly), but speed performance is not the issue with valgrind because
it check all memory allocations/desallocations completed by the program.

Reproduce all action in digiKam using valgrind, all post all error console
messages provides by valgrind.

Thanks in advance.
--
Gilles Caulier
_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users
Reply | Threaded
Open this post in threaded view
|

Re: memory consume

Duncan Hill-5
On Tuesday 10 January 2006 10:29, Gilles Caulier wrote:

> I had no PTP camera, only USB mass storage here to test.

Gilles, if you have the Dynax 5D, it can be converted to PTP mode in the menu
(at least mine can).  Choose the * like option -> Transfer mode -> PTP.

It seems a fair bit slower than USB mass storage, but it does work.
_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users
Reply | Threaded
Open this post in threaded view
|

Re: memory consume

Gilles Caulier
Le Mardi 10 Janvier 2006 12:17, Duncan Hill a écrit :
> On Tuesday 10 January 2006 10:29, Gilles Caulier wrote:
> > I had no PTP camera, only USB mass storage here to test.
>
> Gilles, if you have the Dynax 5D, it can be converted to PTP mode in the
> menu (at least mine can).  Choose the * like option -> Transfer mode ->
> PTP.
>
> It seems a fair bit slower than USB mass storage, but it does work.

Ah. I will take a look...

Gilles
_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users
Reply | Threaded
Open this post in threaded view
|

Re: memory consume

Martin Ehmke
In reply to this post by Gilles Caulier
Hi,

could you test it?

Unfortunately I don't have the tools currently to do that and also only little
time.

Btw: Until now I have only seen the export to static HTML-Pages. Then there is
the KIPI script for exporting to "gallery" php image gallery but are there
currently any further possibilities to export at least digikam comments
(better would be even kind of tag-structure export) to a php/sql image
database?

Martin


On Tuesday 10 January 2006 12:29, Gilles Caulier wrote:

> The better way to check memory leak is to use valgrind tool like this :
>
> valgrind --tool=memcheck --leak-check=full --error-limit=no digikam
>
> note that digikam must be compiled using all debug information to get witch
> source code line(s) are in default.
>
> I had no PTP camera, only USB mass storage here to test.
>
> When you run digikam under valgrind, the speed is very low ( divide per 15
> approximativly), but speed performance is not the issue with valgrind
> because it check all memory allocations/desallocations completed by the
> program.
>
> Reproduce all action in digiKam using valgrind, all post all error console
> messages provides by valgrind.
>
> Thanks in advance.

_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users