digikam 1.2.0 slows down

[Dr. Martin Senftleben]

Hi,

I'm using 1.2.0 as it is the currently available version for LinuxMint.
Desktop is Gnome. DigiKam is a marvellous tool! However, I have
performance problems. Back from vacation, I have to work my way through
about 15.000 pictures. Initially they are all in one folder, so I can
separate the good from the bad ones.
I give tags, comments, evaluate the images, crop and rotate a few and
then move them to their respective places = other folders. I use, as is
obvious, also the editor.
After having gone through about 100 images in this manner, I find that
digikam slows down quite a bit, up to the point that I have to wait for
a minute for changes to apply to the image I'm just working on. After a
restart, everything is fine again, changes are applied instantaneously.
Is there a way to bypass the need to restart digikam? Is this a known
problem that has been solved in 1.3?

Thanks!

Martin


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

[Tim Jenness]

I have the exact same problem. I think it's leaking somewhere. I can rate photos really quickly but after a hundred or so I feel like I'm walking through molasses. I haven't tried 1.3.0 yet (partly because it takes the gentoo packager so long to update a release).

Tim

2010/7/22 Dr. Martin Senftleben <[hidden email]>

Hi,

I'm using 1.2.0 as it is the currently available version for LinuxMint. Desktop is Gnome. DigiKam is a marvellous tool! However, I have performance problems. Back from vacation, I have to work my way through about 15.000 pictures. Initially they are all in one folder, so I can separate the good from the bad ones.
I give tags, comments, evaluate the images, crop and rotate a few and then move them to their respective places = other folders. I use, as is obvious, also the editor.
After having gone through about 100 images in this manner, I find that digikam slows down quite a bit, up to the point that I have to wait for a minute for changes to apply to the image I'm just working on. After a restart, everything is fine again, changes are applied instantaneously.
Is there a way to bypass the need to restart digikam? Is this a known problem that has been solved in 1.3?

Thanks!

Martin


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

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

[Frank Hommes]

Hi,

is it just digikam that slows down? With digikam 1.3 I have to problem
that it loads all thumbnails into memory until the memory is full. So
the whole system will get slow until I restart digikam.
https://bugs.kde.org/show_bug.cgi?id=243692

Frank

On 07/23/2010 10:26 AM, Tim Jenness wrote:

> I have the exact same problem. I think it's leaking somewhere. I can rate
> photos really quickly but after a hundred or so I feel like I'm walking
> through molasses. I haven't tried 1.3.0 yet (partly because it takes the
> gentoo packager so long to update a release).
>
> Tim
>
> 2010/7/22 Dr. Martin Senftleben<[hidden email]>
>
>> Hi,
>>
>> I'm using 1.2.0 as it is the currently available version for LinuxMint.
>> Desktop is Gnome. DigiKam is a marvellous tool! However, I have performance
>> problems. Back from vacation, I have to work my way through about 15.000
>> pictures. Initially they are all in one folder, so I can separate the good
>> from the bad ones.
>> I give tags, comments, evaluate the images, crop and rotate a few and then
>> move them to their respective places = other folders. I use, as is obvious,
>> also the editor.
>> After having gone through about 100 images in this manner, I find that
>> digikam slows down quite a bit, up to the point that I have to wait for a
>> minute for changes to apply to the image I'm just working on. After a
>> restart, everything is fine again, changes are applied instantaneously.
>> Is there a way to bypass the need to restart digikam? Is this a known
>> problem that has been solved in 1.3?
>>
>> Thanks!
>>
>> Martin
>>
>>
>> _______________________________________________
>> Digikam-users mailing list
>> [hidden email]
>> https://mail.kde.org/mailman/listinfo/digikam-users
>>
>>
>
>
>
> _______________________________________________
> Digikam-users mailing list
> [hidden email]
> https://mail.kde.org/mailman/listinfo/digikam-users

--
Frank Hommes, Bummelberg 37, 44149 Dortmund, Germany
Email: [hidden email], ICQ: 14621277
Homepage: http://www.freanki.net
PGP-Key: http://www.freanki.net/gpg/
_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

[George Bourozikas]

I am using 1.3.0 on a Ubuntu Lucid system and have exactly the same
problem.  I'd be happy to help troubleshooting.

On 07/23/2010 04:26 AM, Tim Jenness wrote:

> I have the exact same problem. I think it's leaking somewhere. I can
> rate photos really quickly but after a hundred or so I feel like I'm
> walking through molasses. I haven't tried 1.3.0 yet (partly because it
> takes the gentoo packager so long to update a release).
>
> Tim
>
> 2010/7/22 Dr. Martin Senftleben <[hidden email]
> <mailto:[hidden email]>>
>
>     Hi,
>
>     I'm using 1.2.0 as it is the currently available version for
>     LinuxMint. Desktop is Gnome. DigiKam is a marvellous tool! However,
>     I have performance problems. Back from vacation, I have to work my
>     way through about 15.000 pictures. Initially they are all in one
>     folder, so I can separate the good from the bad ones.
>     I give tags, comments, evaluate the images, crop and rotate a few
>     and then move them to their respective places = other folders. I
>     use, as is obvious, also the editor.
>     After having gone through about 100 images in this manner, I find
>     that digikam slows down quite a bit, up to the point that I have to
>     wait for a minute for changes to apply to the image I'm just working
>     on. After a restart, everything is fine again, changes are applied
>     instantaneously.
>     Is there a way to bypass the need to restart digikam? Is this a
>     known problem that has been solved in 1.3?
>
>     Thanks!
>
>     Martin
>
>
>     _______________________________________________
>     Digikam-users mailing list
>     [hidden email] <mailto:[hidden email]>
>     https://mail.kde.org/mailman/listinfo/digikam-users
>
>
>
>
> _______________________________________________
> Digikam-users mailing list
> [hidden email]
> https://mail.kde.org/mailman/listinfo/digikam-users

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

[S. Burmeister]

Am Freitag, 23. Juli 2010, 10:19:27 schrieb Dr. Martin Senftleben:
> After having gone through about 100 images in this manner, I find that
> digikam slows down quite a bit, up to the point that I have to wait for
> a minute for changes to apply to the image I'm just working on. After a
> restart, everything is fine again, changes are applied instantaneously.
> Is there a way to bypass the need to restart digikam? Is this a known
> problem that has been solved in 1.3?

If you move/rename folders and pictures it could be related to
https://bugs.kde.org/show_bug.cgi?id=242816

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

[Dr. Martin Senftleben]

Hi,

Am 24.07.2010 14:24, schrieb Sven Burmeister:

> Am Freitag, 23. Juli 2010, 10:19:27 schrieb Dr. Martin Senftleben:
>> After having gone through about 100 images in this manner, I find that
>> digikam slows down quite a bit, up to the point that I have to wait for
>> a minute for changes to apply to the image I'm just working on. After a
>> restart, everything is fine again, changes are applied instantaneously.
>> Is there a way to bypass the need to restart digikam? Is this a known
>> problem that has been solved in 1.3?
>
> If you move/rename folders and pictures it could be related to
> https://bugs.kde.org/show_bug.cgi?id=242816

No, I wasn't moving or renaming any folders, I was only moving images
from within digkam from one folder (album) to another. It doesn't look
like the same or similar problem.

Martin

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

[Daniel Bauer-2]

On Saturday 24 July 2010 16.31:40, Dr. Martin Senftleben wrote:

> Hi,
>
> Am 24.07.2010 14:24, schrieb Sven Burmeister:
> > Am Freitag, 23. Juli 2010, 10:19:27 schrieb Dr. Martin Senftleben:
> >> After having gone through about 100 images in this manner, I find that
> >> digikam slows down quite a bit, up to the point that I have to wait for
> >> a minute for changes to apply to the image I'm just working on. After a
> >> restart, everything is fine again, changes are applied instantaneously.
> >> Is there a way to bypass the need to restart digikam? Is this a known
> >> problem that has been solved in 1.3?
> >
> > If you move/rename folders and pictures it could be related to
> > https://bugs.kde.org/show_bug.cgi?id=242816
>
> No, I wasn't moving or renaming any folders, I was only moving images
> from within digkam from one folder (album) to another. It doesn't look
> like the same or similar problem.
>
> Martin

I experience same behaviour with digiKam Version 1.3.0, KDE 4.4.5 on openSuse
11.2.

I do a selection from a series, move this selection to another folder. Go to
another folder, do a selection, move this to another folder. Go to another
folder, select 50 images, delete them (move to trash)...

Now it takes very long to move oder delete further images, or to show the
thumbs of another thumb, or to open an image in the editor.

Just closing/reopening digikam doesn't help al lot. I have to wait until all
processes of digikam have finished (they don't finish immediately after
closing the app). In my opinion there is no difference, whether I just wait a
while until digikam "gets normal" again or if I close/reopen digikam.

I guess it is a problem of the database. I use the standard database (not
mysql).

However I am already used to it. Also, I have a slow computer anyway...

Daniel

 
--
Daniel Bauer photographer Basel Barcelona
professional photography: http://www.daniel-bauer.com
my new blog: http://www.guapamania.com/wordpress/
_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

[Anders Stedtlund]

Hi,

I might have a similar problem with digiKam 1.3.0 in openSUSE 11.3. I
can see that digiKam takes a lot of ram, over 60% according to top,
after some slideshows. I haven't moved images, just selected images
for different slideshows.

The whole system gets sluggish.

Restart of digiKam is needed. One process takes a lot of time before finishing.

/Anders

2010/7/25 Daniel Bauer <[hidden email]>:

> On Saturday 24 July 2010 16.31:40, Dr. Martin Senftleben wrote:
>> Hi,
>>
>> Am 24.07.2010 14:24, schrieb Sven Burmeister:
>> > Am Freitag, 23. Juli 2010, 10:19:27 schrieb Dr. Martin Senftleben:
>> >> After having gone through about 100 images in this manner, I find that
>> >> digikam slows down quite a bit, up to the point that I have to wait for
>> >> a minute for changes to apply to the image I'm just working on. After a
>> >> restart, everything is fine again, changes are applied instantaneously.
>> >> Is there a way to bypass the need to restart digikam? Is this a known
>> >> problem that has been solved in 1.3?
>> >
>> > If you move/rename folders and pictures it could be related to
>> > https://bugs.kde.org/show_bug.cgi?id=242816
>>
>> No, I wasn't moving or renaming any folders, I was only moving images
>> from within digkam from one folder (album) to another. It doesn't look
>> like the same or similar problem.
>>
>> Martin
>
> I experience same behaviour with digiKam Version 1.3.0, KDE 4.4.5 on openSuse
> 11.2.
>
> I do a selection from a series, move this selection to another folder. Go to
> another folder, do a selection, move this to another folder. Go to another
> folder, select 50 images, delete them (move to trash)...
>
> Now it takes very long to move oder delete further images, or to show the
> thumbs of another thumb, or to open an image in the editor.
>
> Just closing/reopening digikam doesn't help al lot. I have to wait until all
> processes of digikam have finished (they don't finish immediately after
> closing the app). In my opinion there is no difference, whether I just wait a
> while until digikam "gets normal" again or if I close/reopen digikam.
>
> I guess it is a problem of the database. I use the standard database (not
> mysql).
>
> However I am already used to it. Also, I have a slow computer anyway...
>
> Daniel
>
>
> --
> Daniel Bauer photographer Basel Barcelona
> professional photography: http://www.daniel-bauer.com
> my new blog: http://www.guapamania.com/wordpress/
> _______________________________________________
> Digikam-users mailing list
> [hidden email]
> https://mail.kde.org/mailman/listinfo/digikam-users
>

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

[Gilles Caulier-4]

I cannot reproduce this memory leak under Mandriva 2010.1.

I processed this week end more than 130 RAW image taken with my Sony
Alpha 500. Tagging, comparing, sorting, demosaicing, editing (ratio
crop, color corrections) saving to PNG, export to JPEG (via BQM)...

No problem : Double core 2.5 Ghz (32bits) + 4 GB RAM. digiKam +
kipi-plugins + kdegraphics/libs + Exiv2 from trunk

Do you use 64 bits system ?

Can you take a look memory leak with valgrind :

http://lxr.kde.org/source/extragear/graphics/digikam/HACKING#241

Gilles Caulier

2010/7/25 Stedtlund <[hidden email]>:

> Hi,
>
> I might have a similar problem with digiKam 1.3.0 in openSUSE 11.3. I
> can see that digiKam takes a lot of ram, over 60% according to top,
> after some slideshows. I haven't moved images, just selected images
> for different slideshows.
>
> The whole system gets sluggish.
>
> Restart of digiKam is needed. One process takes a lot of time before finishing.
>
> /Anders
>
> 2010/7/25 Daniel Bauer <[hidden email]>:
>> On Saturday 24 July 2010 16.31:40, Dr. Martin Senftleben wrote:
>>> Hi,
>>>
>>> Am 24.07.2010 14:24, schrieb Sven Burmeister:
>>> > Am Freitag, 23. Juli 2010, 10:19:27 schrieb Dr. Martin Senftleben:
>>> >> After having gone through about 100 images in this manner, I find that
>>> >> digikam slows down quite a bit, up to the point that I have to wait for
>>> >> a minute for changes to apply to the image I'm just working on. After a
>>> >> restart, everything is fine again, changes are applied instantaneously.
>>> >> Is there a way to bypass the need to restart digikam? Is this a known
>>> >> problem that has been solved in 1.3?
>>> >
>>> > If you move/rename folders and pictures it could be related to
>>> > https://bugs.kde.org/show_bug.cgi?id=242816
>>>
>>> No, I wasn't moving or renaming any folders, I was only moving images
>>> from within digkam from one folder (album) to another. It doesn't look
>>> like the same or similar problem.
>>>
>>> Martin
>>
>> I experience same behaviour with digiKam Version 1.3.0, KDE 4.4.5 on openSuse
>> 11.2.
>>
>> I do a selection from a series, move this selection to another folder. Go to
>> another folder, do a selection, move this to another folder. Go to another
>> folder, select 50 images, delete them (move to trash)...
>>
>> Now it takes very long to move oder delete further images, or to show the
>> thumbs of another thumb, or to open an image in the editor.
>>
>> Just closing/reopening digikam doesn't help al lot. I have to wait until all
>> processes of digikam have finished (they don't finish immediately after
>> closing the app). In my opinion there is no difference, whether I just wait a
>> while until digikam "gets normal" again or if I close/reopen digikam.
>>
>> I guess it is a problem of the database. I use the standard database (not
>> mysql).
>>
>> However I am already used to it. Also, I have a slow computer anyway...
>>
>> Daniel
>>
>>
>> --
>> Daniel Bauer photographer Basel Barcelona
>> professional photography: http://www.daniel-bauer.com
>> my new blog: http://www.guapamania.com/wordpress/
>> _______________________________________________
>> Digikam-users mailing list
>> [hidden email]
>> https://mail.kde.org/mailman/listinfo/digikam-users
>>
> _______________________________________________
> Digikam-users mailing list
> [hidden email]
> https://mail.kde.org/mailman/listinfo/digikam-users
>

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

[Tim Jenness]

For me it happens when I'm rating. I do a sequence like "Ctrl-N, space, Ctrl-N, space..." etc where "N" is a rating 1-5 and I'm viewing the album one image at a time. The first few are lightning fast but a few hundred in it's crawling and I have to restart digikam.

Tim

On Sun, Jul 25, 2010 at 6:03 AM, Gilles Caulier <[hidden email]> wrote:

I cannot reproduce this memory leak under Mandriva 2010.1.

I processed this week end more than 130 RAW image taken with my Sony
Alpha 500. Tagging, comparing, sorting, demosaicing, editing (ratio
crop, color corrections) saving to PNG, export to JPEG (via BQM)...

No problem : Double core 2.5 Ghz (32bits) + 4 GB RAM. digiKam +
kipi-plugins + kdegraphics/libs + Exiv2 from trunk

Do you use 64 bits system ?

Can you take a look memory leak with valgrind :

http://lxr.kde.org/source/extragear/graphics/digikam/HACKING#241

Gilles Caulier

2010/7/25 Stedtlund <[hidden email]>:

> Hi,
>
> I might have a similar problem with digiKam 1.3.0 in openSUSE 11.3. I
> can see that digiKam takes a lot of ram, over 60% according to top,
> after some slideshows. I haven't moved images, just selected images
> for different slideshows.
>
> The whole system gets sluggish.
>
> Restart of digiKam is needed. One process takes a lot of time before finishing.
>
> /Anders
>
> 2010/7/25 Daniel Bauer <[hidden email]>:
>> On Saturday 24 July 2010 16.31:40, Dr. Martin Senftleben wrote:
>>> Hi,
>>>
>>> Am 24.07.2010 14:24, schrieb Sven Burmeister:
>>> > Am Freitag, 23. Juli 2010, 10:19:27 schrieb Dr. Martin Senftleben:
>>> >> After having gone through about 100 images in this manner, I find that
>>> >> digikam slows down quite a bit, up to the point that I have to wait for
>>> >> a minute for changes to apply to the image I'm just working on. After a
>>> >> restart, everything is fine again, changes are applied instantaneously.
>>> >> Is there a way to bypass the need to restart digikam? Is this a known
>>> >> problem that has been solved in 1.3?
>>> >
>>> > If you move/rename folders and pictures it could be related to
>>> > https://bugs.kde.org/show_bug.cgi?id=242816
>>>
>>> No, I wasn't moving or renaming any folders, I was only moving images
>>> from within digkam from one folder (album) to another. It doesn't look
>>> like the same or similar problem.
>>>
>>> Martin
>>
>> I experience same behaviour with digiKam Version 1.3.0, KDE 4.4.5 on openSuse
>> 11.2.
>>
>> I do a selection from a series, move this selection to another folder. Go to
>> another folder, do a selection, move this to another folder. Go to another
>> folder, select 50 images, delete them (move to trash)...
>>
>> Now it takes very long to move oder delete further images, or to show the
>> thumbs of another thumb, or to open an image in the editor.
>>
>> Just closing/reopening digikam doesn't help al lot. I have to wait until all
>> processes of digikam have finished (they don't finish immediately after
>> closing the app). In my opinion there is no difference, whether I just wait a
>> while until digikam "gets normal" again or if I close/reopen digikam.
>>
>> I guess it is a problem of the database. I use the standard database (not
>> mysql).
>>
>> However I am already used to it. Also, I have a slow computer anyway...
>>
>> Daniel
>>
>>
>> --
>> Daniel Bauer photographer Basel Barcelona
>> professional photography: http://www.daniel-bauer.com
>> my new blog: http://www.guapamania.com/wordpress/
>> _______________________________________________
>> Digikam-users mailing list
>> [hidden email]
>> https://mail.kde.org/mailman/listinfo/digikam-users
>>
> _______________________________________________
> Digikam-users mailing list
> [hidden email]
> https://mail.kde.org/mailman/listinfo/digikam-users
>
_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

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

[Tim Jenness]

and sorry. I'm on gentoo 64-bit.

On Sun, Jul 25, 2010 at 8:30 PM, Tim Jenness <[hidden email]> wrote:

For me it happens when I'm rating. I do a sequence like "Ctrl-N, space, Ctrl-N, space..." etc where "N" is a rating 1-5 and I'm viewing the album one image at a time. The first few are lightning fast but a few hundred in it's crawling and I have to restart digikam.

Tim

On Sun, Jul 25, 2010 at 6:03 AM, Gilles Caulier <[hidden email]> wrote:

I cannot reproduce this memory leak under Mandriva 2010.1.

I processed this week end more than 130 RAW image taken with my Sony
Alpha 500. Tagging, comparing, sorting, demosaicing, editing (ratio
crop, color corrections) saving to PNG, export to JPEG (via BQM)...

No problem : Double core 2.5 Ghz (32bits) + 4 GB RAM. digiKam +
kipi-plugins + kdegraphics/libs + Exiv2 from trunk

Do you use 64 bits system ?

Can you take a look memory leak with valgrind :

http://lxr.kde.org/source/extragear/graphics/digikam/HACKING#241

Gilles Caulier

2010/7/25 Stedtlund <[hidden email]>:

> Hi,
>
> I might have a similar problem with digiKam 1.3.0 in openSUSE 11.3. I
> can see that digiKam takes a lot of ram, over 60% according to top,
> after some slideshows. I haven't moved images, just selected images
> for different slideshows.
>
> The whole system gets sluggish.
>
> Restart of digiKam is needed. One process takes a lot of time before finishing.
>
> /Anders
>
> 2010/7/25 Daniel Bauer <[hidden email]>:
>> On Saturday 24 July 2010 16.31:40, Dr. Martin Senftleben wrote:
>>> Hi,
>>>
>>> Am 24.07.2010 14:24, schrieb Sven Burmeister:
>>> > Am Freitag, 23. Juli 2010, 10:19:27 schrieb Dr. Martin Senftleben:
>>> >> After having gone through about 100 images in this manner, I find that
>>> >> digikam slows down quite a bit, up to the point that I have to wait for
>>> >> a minute for changes to apply to the image I'm just working on. After a
>>> >> restart, everything is fine again, changes are applied instantaneously.
>>> >> Is there a way to bypass the need to restart digikam? Is this a known
>>> >> problem that has been solved in 1.3?
>>> >
>>> > If you move/rename folders and pictures it could be related to
>>> > https://bugs.kde.org/show_bug.cgi?id=242816
>>>
>>> No, I wasn't moving or renaming any folders, I was only moving images
>>> from within digkam from one folder (album) to another. It doesn't look
>>> like the same or similar problem.
>>>
>>> Martin
>>
>> I experience same behaviour with digiKam Version 1.3.0, KDE 4.4.5 on openSuse
>> 11.2.
>>
>> I do a selection from a series, move this selection to another folder. Go to
>> another folder, do a selection, move this to another folder. Go to another
>> folder, select 50 images, delete them (move to trash)...
>>
>> Now it takes very long to move oder delete further images, or to show the
>> thumbs of another thumb, or to open an image in the editor.
>>
>> Just closing/reopening digikam doesn't help al lot. I have to wait until all
>> processes of digikam have finished (they don't finish immediately after
>> closing the app). In my opinion there is no difference, whether I just wait a
>> while until digikam "gets normal" again or if I close/reopen digikam.
>>
>> I guess it is a problem of the database. I use the standard database (not
>> mysql).
>>
>> However I am already used to it. Also, I have a slow computer anyway...
>>
>> Daniel
>>
>>
>> --
>> Daniel Bauer photographer Basel Barcelona
>> professional photography: http://www.daniel-bauer.com
>> my new blog: http://www.guapamania.com/wordpress/
>> _______________________________________________
>> Digikam-users mailing list
>> [hidden email]
>> https://mail.kde.org/mailman/listinfo/digikam-users
>>
> _______________________________________________
> Digikam-users mailing list
> [hidden email]
> https://mail.kde.org/mailman/listinfo/digikam-users
>
_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

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

[Anders Stedtlund]

I have to revise my sightings now. It doesn't seem to be related to
slideshows as I first stated.

I have the option selected to show images for sub albums when
selecting an album. This implies when I select the root album, all my
images will be visible as thumbnails. Allmost 11000 images. When I do
this, digiKam seems to cache the thumbnails, or something else, in
memory. Is this the case? The memory footprint when doing this will
soon rise to more than 70% of available ram. If using other
applications at the same time, swaping will hit in. The memory
footprint wont go down until digiKam is restarted.

I have never used valgrind before, so the behaviour might be allright.
When using valgrind digiKam is almost unusable. Everything takes uge
amount of time to happen.

I'm on openSUSE 11.3, 64 bit. 3 GB of ram.


2010/7/25 Gilles Caulier <[hidden email]>:

> I cannot reproduce this memory leak under Mandriva 2010.1.
>
> I processed this week end more than 130 RAW image taken with my Sony
> Alpha 500. Tagging, comparing, sorting, demosaicing, editing (ratio
> crop, color corrections) saving to PNG, export to JPEG (via BQM)...
>
> No problem : Double core 2.5 Ghz (32bits) + 4 GB RAM. digiKam +
> kipi-plugins + kdegraphics/libs + Exiv2 from trunk
>
> Do you use 64 bits system ?
>
> Can you take a look memory leak with valgrind :
>
> http://lxr.kde.org/source/extragear/graphics/digikam/HACKING#241
>
> Gilles Caulier
>
> 2010/7/25 Stedtlund <[hidden email]>:
>> Hi,
>>
>> I might have a similar problem with digiKam 1.3.0 in openSUSE 11.3. I
>> can see that digiKam takes a lot of ram, over 60% according to top,
>> after some slideshows. I haven't moved images, just selected images
>> for different slideshows.
>>
>> The whole system gets sluggish.
>>
>> Restart of digiKam is needed. One process takes a lot of time before finishing.
>>
>> /Anders
>>
>> 2010/7/25 Daniel Bauer <[hidden email]>:
>>> On Saturday 24 July 2010 16.31:40, Dr. Martin Senftleben wrote:
>>>> Hi,
>>>>
>>>> Am 24.07.2010 14:24, schrieb Sven Burmeister:
>>>> > Am Freitag, 23. Juli 2010, 10:19:27 schrieb Dr. Martin Senftleben:
>>>> >> After having gone through about 100 images in this manner, I find that
>>>> >> digikam slows down quite a bit, up to the point that I have to wait for
>>>> >> a minute for changes to apply to the image I'm just working on. After a
>>>> >> restart, everything is fine again, changes are applied instantaneously.
>>>> >> Is there a way to bypass the need to restart digikam? Is this a known
>>>> >> problem that has been solved in 1.3?
>>>> >
>>>> > If you move/rename folders and pictures it could be related to
>>>> > https://bugs.kde.org/show_bug.cgi?id=242816
>>>>
>>>> No, I wasn't moving or renaming any folders, I was only moving images
>>>> from within digkam from one folder (album) to another. It doesn't look
>>>> like the same or similar problem.
>>>>
>>>> Martin
>>>
>>> I experience same behaviour with digiKam Version 1.3.0, KDE 4.4.5 on openSuse
>>> 11.2.
>>>
>>> I do a selection from a series, move this selection to another folder. Go to
>>> another folder, do a selection, move this to another folder. Go to another
>>> folder, select 50 images, delete them (move to trash)...
>>>
>>> Now it takes very long to move oder delete further images, or to show the
>>> thumbs of another thumb, or to open an image in the editor.
>>>
>>> Just closing/reopening digikam doesn't help al lot. I have to wait until all
>>> processes of digikam have finished (they don't finish immediately after
>>> closing the app). In my opinion there is no difference, whether I just wait a
>>> while until digikam "gets normal" again or if I close/reopen digikam.
>>>
>>> I guess it is a problem of the database. I use the standard database (not
>>> mysql).
>>>
>>> However I am already used to it. Also, I have a slow computer anyway...
>>>
>>> Daniel
>>>
>>>
>>> --
>>> Daniel Bauer photographer Basel Barcelona
>>> professional photography: http://www.daniel-bauer.com
>>> my new blog: http://www.guapamania.com/wordpress/
>>> _______________________________________________
>>> Digikam-users mailing list
>>> [hidden email]
>>> https://mail.kde.org/mailman/listinfo/digikam-users
>>>
>> _______________________________________________
>> Digikam-users mailing list
>> [hidden email]
>> https://mail.kde.org/mailman/listinfo/digikam-users
>>
> _______________________________________________
> Digikam-users mailing list
> [hidden email]
> https://mail.kde.org/mailman/listinfo/digikam-users
>

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

[Photonoxx]

I think I encounter the same kind of thing with my configuration (Ubuntu  
10.04 64bits - Digikam 1.3).

It happens sometime (but not too often) when I'm tagging multiple photos  
or when I'm rating one by one like Tim (with pageup or pagedown, Ctrl+N,  
pageup or pagedown, etc...).

What happens, is that Digikam seems to stop for a certain time (may be  
between 10-30 seconds) and continue after that without any matter.

I have system monitor applet in my menu bar in gnome, and at this moment,  
I can see the CPU occupation is approx 100%, but not due to software usage  
but, apparently for "latence E/S" (I/O latency ?) usage (the graph show  
dark blue)...

Nicolas


Le Mon, 26 Jul 2010 08:30:16 +0200, Tim Jenness <[hidden email]> a  
écrit:

> For me it happens when I'm rating. I do a sequence like "Ctrl-N, space,
> Ctrl-N, space..." etc where "N" is a rating 1-5 and I'm viewing the album
> one image at a time. The first few are lightning fast but a few hundred  
> in
> it's crawling and I have to restart digikam.
>
> Tim
>
> On Sun, Jul 25, 2010 at 6:03 AM, Gilles Caulier  
> <[hidden email]>wrote:
>
>> I cannot reproduce this memory leak under Mandriva 2010.1.
>>
>> I processed this week end more than 130 RAW image taken with my Sony
>> Alpha 500. Tagging, comparing, sorting, demosaicing, editing (ratio
>> crop, color corrections) saving to PNG, export to JPEG (via BQM)...
>>
>> No problem : Double core 2.5 Ghz (32bits) + 4 GB RAM. digiKam +
>> kipi-plugins + kdegraphics/libs + Exiv2 from trunk
>>
>> Do you use 64 bits system ?
>>
>> Can you take a look memory leak with valgrind :
>>
>> http://lxr.kde.org/source/extragear/graphics/digikam/HACKING#241
>>
>> Gilles Caulier
>>
>> 2010/7/25 Stedtlund <[hidden email]>:
>> > Hi,
>> >
>> > I might have a similar problem with digiKam 1.3.0 in openSUSE 11.3. I
>> > can see that digiKam takes a lot of ram, over 60% according to top,
>> > after some slideshows. I haven't moved images, just selected images
>> > for different slideshows.
>> >
>> > The whole system gets sluggish.
>> >
>> > Restart of digiKam is needed. One process takes a lot of time before
>> finishing.
>> >
>> > /Anders
>> >
>> > 2010/7/25 Daniel Bauer <[hidden email]>:
>> >> On Saturday 24 July 2010 16.31:40, Dr. Martin Senftleben wrote:
>> >>> Hi,
>> >>>
>> >>> Am 24.07.2010 14:24, schrieb Sven Burmeister:
>> >>> > Am Freitag, 23. Juli 2010, 10:19:27 schrieb Dr. Martin Senftleben:
>> >>> >> After having gone through about 100 images in this manner, I find
>> that
>> >>> >> digikam slows down quite a bit, up to the point that I have to  
>> wait
>> for
>> >>> >> a minute for changes to apply to the image I'm just working on.
>> After a
>> >>> >> restart, everything is fine again, changes are applied
>> instantaneously.
>> >>> >> Is there a way to bypass the need to restart digikam? Is this a
>> known
>> >>> >> problem that has been solved in 1.3?
>> >>> >
>> >>> > If you move/rename folders and pictures it could be related to
>> >>> > https://bugs.kde.org/show_bug.cgi?id=242816
>> >>>
>> >>> No, I wasn't moving or renaming any folders, I was only moving  
>> images
>> >>> from within digkam from one folder (album) to another. It doesn't  
>> look
>> >>> like the same or similar problem.
>> >>>
>> >>> Martin
>> >>
>> >> I experience same behaviour with digiKam Version 1.3.0, KDE 4.4.5 on
>> openSuse
>> >> 11.2.
>> >>
>> >> I do a selection from a series, move this selection to another  
>> folder.
>> Go to
>> >> another folder, do a selection, move this to another folder. Go to
>> another
>> >> folder, select 50 images, delete them (move to trash)...
>> >>
>> >> Now it takes very long to move oder delete further images, or to show
>> the
>> >> thumbs of another thumb, or to open an image in the editor.
>> >>
>> >> Just closing/reopening digikam doesn't help al lot. I have to wait  
>> until
>> all
>> >> processes of digikam have finished (they don't finish immediately  
>> after
>> >> closing the app). In my opinion there is no difference, whether I  
>> just
>> wait a
>> >> while until digikam "gets normal" again or if I close/reopen digikam.
>> >>
>> >> I guess it is a problem of the database. I use the standard database
>> (not
>> >> mysql).
>> >>
>> >> However I am already used to it. Also, I have a slow computer  
>> anyway...
>> >>
>> >> Daniel
>> >>
>> >>
>> >> --
>> >> Daniel Bauer photographer Basel Barcelona
>> >> professional photography: http://www.daniel-bauer.com
>> >> my new blog: http://www.guapamania.com/wordpress/
>> >> _______________________________________________
>> >> Digikam-users mailing list
>> >> [hidden email]
>> >> https://mail.kde.org/mailman/listinfo/digikam-users
>> >>
>> > _______________________________________________
>> > Digikam-users mailing list
>> > [hidden email]
>> > https://mail.kde.org/mailman/listinfo/digikam-users
>> >
>> _______________________________________________
>> Digikam-users mailing list
>> [hidden email]
>> https://mail.kde.org/mailman/listinfo/digikam-users
>>

--
Nicolas Boulesteix - Chasseur de lueurs - http://www.photonoxx.fr
_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

[Tim Jenness]

and doing the obvious thing of looking at top I see that kio_thumbnail is taking between 30 and 65% of my CPU and 10% of my RAM (450MB) even when I'm not using digikam. digikam itself is at 0% CPU with 5% of RAM.

Tim

On Sun, Jul 25, 2010 at 8:30 PM, Tim Jenness <[hidden email]> wrote:

and sorry. I'm on gentoo 64-bit.

On Sun, Jul 25, 2010 at 8:30 PM, Tim Jenness <[hidden email]> wrote:

For me it happens when I'm rating. I do a sequence like "Ctrl-N, space, Ctrl-N, space..." etc where "N" is a rating 1-5 and I'm viewing the album one image at a time. The first few are lightning fast but a few hundred in it's crawling and I have to restart digikam.

Tim

On Sun, Jul 25, 2010 at 6:03 AM, Gilles Caulier <[hidden email]> wrote:

I cannot reproduce this memory leak under Mandriva 2010.1.

I processed this week end more than 130 RAW image taken with my Sony
Alpha 500. Tagging, comparing, sorting, demosaicing, editing (ratio
crop, color corrections) saving to PNG, export to JPEG (via BQM)...

No problem : Double core 2.5 Ghz (32bits) + 4 GB RAM. digiKam +
kipi-plugins + kdegraphics/libs + Exiv2 from trunk

Do you use 64 bits system ?

Can you take a look memory leak with valgrind :

http://lxr.kde.org/source/extragear/graphics/digikam/HACKING#241

Gilles Caulier

2010/7/25 Stedtlund <[hidden email]>:

> Hi,
>
> I might have a similar problem with digiKam 1.3.0 in openSUSE 11.3. I
> can see that digiKam takes a lot of ram, over 60% according to top,
> after some slideshows. I haven't moved images, just selected images
> for different slideshows.
>
> The whole system gets sluggish.
>
> Restart of digiKam is needed. One process takes a lot of time before finishing.
>
> /Anders
>
> 2010/7/25 Daniel Bauer <[hidden email]>:
>> On Saturday 24 July 2010 16.31:40, Dr. Martin Senftleben wrote:
>>> Hi,
>>>
>>> Am 24.07.2010 14:24, schrieb Sven Burmeister:
>>> > Am Freitag, 23. Juli 2010, 10:19:27 schrieb Dr. Martin Senftleben:
>>> >> After having gone through about 100 images in this manner, I find that
>>> >> digikam slows down quite a bit, up to the point that I have to wait for
>>> >> a minute for changes to apply to the image I'm just working on. After a
>>> >> restart, everything is fine again, changes are applied instantaneously.
>>> >> Is there a way to bypass the need to restart digikam? Is this a known
>>> >> problem that has been solved in 1.3?
>>> >
>>> > If you move/rename folders and pictures it could be related to
>>> > https://bugs.kde.org/show_bug.cgi?id=242816
>>>
>>> No, I wasn't moving or renaming any folders, I was only moving images
>>> from within digkam from one folder (album) to another. It doesn't look
>>> like the same or similar problem.
>>>
>>> Martin
>>
>> I experience same behaviour with digiKam Version 1.3.0, KDE 4.4.5 on openSuse
>> 11.2.
>>
>> I do a selection from a series, move this selection to another folder. Go to
>> another folder, do a selection, move this to another folder. Go to another
>> folder, select 50 images, delete them (move to trash)...
>>
>> Now it takes very long to move oder delete further images, or to show the
>> thumbs of another thumb, or to open an image in the editor.
>>
>> Just closing/reopening digikam doesn't help al lot. I have to wait until all
>> processes of digikam have finished (they don't finish immediately after
>> closing the app). In my opinion there is no difference, whether I just wait a
>> while until digikam "gets normal" again or if I close/reopen digikam.
>>
>> I guess it is a problem of the database. I use the standard database (not
>> mysql).
>>
>> However I am already used to it. Also, I have a slow computer anyway...
>>
>> Daniel
>>
>>
>> --
>> Daniel Bauer photographer Basel Barcelona
>> professional photography: http://www.daniel-bauer.com
>> my new blog: http://www.guapamania.com/wordpress/
>> _______________________________________________
>> Digikam-users mailing list
>> [hidden email]
>> https://mail.kde.org/mailman/listinfo/digikam-users
>>
> _______________________________________________
> Digikam-users mailing list
> [hidden email]
> https://mail.kde.org/mailman/listinfo/digikam-users
>
_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

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

[Johannes Wienke-2]

Marcel,

could this be related to your changes for the preview loading?

Johannes

Tim Jenness wrote:

> and doing the obvious thing of looking at top I see that kio_thumbnail is
> taking between 30 and 65% of my CPU and 10% of my RAM (450MB) even when I'm
> not using digikam. digikam itself is at 0% CPU with 5% of RAM.
>
> Tim
>
> On Sun, Jul 25, 2010 at 8:30 PM, Tim Jenness <[hidden email]> wrote:
>
>> and sorry. I'm on gentoo 64-bit.
>>
>>
>> On Sun, Jul 25, 2010 at 8:30 PM, Tim Jenness <[hidden email]>wrote:
>>
>>> For me it happens when I'm rating. I do a sequence like "Ctrl-N, space,
>>> Ctrl-N, space..." etc where "N" is a rating 1-5 and I'm viewing the album
>>> one image at a time. The first few are lightning fast but a few hundred in
>>> it's crawling and I have to restart digikam.
>>>
>>> Tim
>>>
>>>
>>> On Sun, Jul 25, 2010 at 6:03 AM, Gilles Caulier <[hidden email]
>>>> wrote:
>>>> I cannot reproduce this memory leak under Mandriva 2010.1.
>>>>
>>>> I processed this week end more than 130 RAW image taken with my Sony
>>>> Alpha 500. Tagging, comparing, sorting, demosaicing, editing (ratio
>>>> crop, color corrections) saving to PNG, export to JPEG (via BQM)...
>>>>
>>>> No problem : Double core 2.5 Ghz (32bits) + 4 GB RAM. digiKam +
>>>> kipi-plugins + kdegraphics/libs + Exiv2 from trunk
>>>>
>>>> Do you use 64 bits system ?
>>>>
>>>> Can you take a look memory leak with valgrind :
>>>>
>>>> http://lxr.kde.org/source/extragear/graphics/digikam/HACKING#241
>>>>
>>>> Gilles Caulier
>>>>
>>>> 2010/7/25 Stedtlund <[hidden email]>:
>>>>> Hi,
>>>>>
>>>>> I might have a similar problem with digiKam 1.3.0 in openSUSE 11.3. I
>>>>> can see that digiKam takes a lot of ram, over 60% according to top,
>>>>> after some slideshows. I haven't moved images, just selected images
>>>>> for different slideshows.
>>>>>
>>>>> The whole system gets sluggish.
>>>>>
>>>>> Restart of digiKam is needed. One process takes a lot of time before
>>>> finishing.
>>>>> /Anders
>>>>>
>>>>> 2010/7/25 Daniel Bauer <[hidden email]>:
>>>>>> On Saturday 24 July 2010 16.31:40, Dr. Martin Senftleben wrote:
>>>>>>> Hi,
>>>>>>>
>>>>>>> Am 24.07.2010 14:24, schrieb Sven Burmeister:
>>>>>>>> Am Freitag, 23. Juli 2010, 10:19:27 schrieb Dr. Martin Senftleben:
>>>>>>>>> After having gone through about 100 images in this manner, I find
>>>> that
>>>>>>>>> digikam slows down quite a bit, up to the point that I have to
>>>> wait for
>>>>>>>>> a minute for changes to apply to the image I'm just working on.
>>>> After a
>>>>>>>>> restart, everything is fine again, changes are applied
>>>> instantaneously.
>>>>>>>>> Is there a way to bypass the need to restart digikam? Is this a
>>>> known
>>>>>>>>> problem that has been solved in 1.3?
>>>>>>>> If you move/rename folders and pictures it could be related to
>>>>>>>> https://bugs.kde.org/show_bug.cgi?id=242816
>>>>>>> No, I wasn't moving or renaming any folders, I was only moving images
>>>>>>> from within digkam from one folder (album) to another. It doesn't
>>>> look
>>>>>>> like the same or similar problem.
>>>>>>>
>>>>>>> Martin
>>>>>> I experience same behaviour with digiKam Version 1.3.0, KDE 4.4.5 on
>>>> openSuse
>>>>>> 11.2.
>>>>>>
>>>>>> I do a selection from a series, move this selection to another folder.
>>>> Go to
>>>>>> another folder, do a selection, move this to another folder. Go to
>>>> another
>>>>>> folder, select 50 images, delete them (move to trash)...
>>>>>>
>>>>>> Now it takes very long to move oder delete further images, or to show
>>>> the
>>>>>> thumbs of another thumb, or to open an image in the editor.
>>>>>>
>>>>>> Just closing/reopening digikam doesn't help al lot. I have to wait
>>>> until all
>>>>>> processes of digikam have finished (they don't finish immediately
>>>> after
>>>>>> closing the app). In my opinion there is no difference, whether I just
>>>> wait a
>>>>>> while until digikam "gets normal" again or if I close/reopen digikam.
>>>>>>
>>>>>> I guess it is a problem of the database. I use the standard database
>>>> (not
>>>>>> mysql).
>>>>>>
>>>>>> However I am already used to it. Also, I have a slow computer
>>>> anyway...
>>>>>> Daniel
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Daniel Bauer photographer Basel Barcelona
>>>>>> professional photography: http://www.daniel-bauer.com
>>>>>> my new blog: http://www.guapamania.com/wordpress/
>>>>>> _______________________________________________
>>>>>> Digikam-users mailing list
>>>>>> [hidden email]
>>>>>> https://mail.kde.org/mailman/listinfo/digikam-users
>>>>>>
>>>>> _______________________________________________
>>>>> Digikam-users mailing list
>>>>> [hidden email]
>>>>> https://mail.kde.org/mailman/listinfo/digikam-users
>>>>>
>>>> _______________________________________________
>>>> Digikam-users mailing list
>>>> [hidden email]
>>>> https://mail.kde.org/mailman/listinfo/digikam-users
>>>>
>>>
>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> Digikam-users mailing list
> [hidden email]
> https://mail.kde.org/mailman/listinfo/digikam-users

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

[Marcel Wiesweg]

> Marcel,
>
> could this be related to your changes for the preview loading?
>
> Johannes
>
> Tim Jenness wrote:
> > and doing the obvious thing of looking at top I see that kio_thumbnail is
> > taking between 30 and 65% of my CPU and 10% of my RAM (450MB) even when
> > I'm not using digikam. digikam itself is at 0% CPU with 5% of RAM.

I did not follow the full discussion yet. Usually we dont use kio_thumbnail
for normal pictures, but if there's video files, it will be used.
But only once at thumbnail creation.


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