thumbnail generation
Locked
 
|
Hallo
thumbnail regeneration in menu extra->maintainance is a little buggy here (recent digikam 3.4 on fedora 19, 64bit). It allocates new memory for every photo but never gives the memory back. If all memory (8G) and swap (10G) are used, the OOM-process of the kernel kills digikam. Anyone seeing this issue as well? Regards Martin _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
|
|
Hm
I tried it with another user on a different computer (same software) and had no problem to generate the thumbnails. IS there something in the setup that changes thumbnail behaviour? Regards Martin Am 27.09.2013 20:35, schrieb Martin (KDE): > Hallo > > thumbnail regeneration in menu extra->maintainance is a little buggy > here (recent digikam 3.4 on fedora 19, 64bit). It allocates new memory > for every photo but never gives the memory back. If all memory (8G) and > swap (10G) are used, the OOM-process of the kernel kills digikam. Anyone > seeing this issue as well? > > Regards > 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 |
|
|
Martin - just a thought or perhaps a suggestion.
I run digikam 3.4.0 on openSUSE 12.3 with KDE 4.11.1. I have noticed that on occasion the digikam links into KDE get all confused if an update (to KDE components) is run while digikam is open or , for some, if I don't restart KDE. I typically logout my user and log back in to get a KDE restart. This sounds like a config mismatch, perhaps in your ~/.kde4 folder. The most frequent suggestion on the openSUSE forum for situations like this - create a new user account (and get a "clean ~/.kde4) and try it as that new user. Relatively simple and does not damage your user profile. The brute force approach is to rename your ~/.kde4 as ~/.kde4_old and restart KDE which will get you a new ~/.kde4. That of course wipes a lot of customization you may have on your desktop Good Luck On 09/28/2013 09:38 AM, Martin (KDE) wrote: > Hm > > I tried it with another user on a different computer (same software) and > had no problem to generate the thumbnails. IS there something in the > setup that changes thumbnail behaviour? > > Regards > Martin > > Am 27.09.2013 20:35, schrieb Martin (KDE): >> Hallo >> >> thumbnail regeneration in menu extra->maintainance is a little buggy >> here (recent digikam 3.4 on fedora 19, 64bit). It allocates new memory >> for every photo but never gives the memory back. If all memory (8G) and >> swap (10G) are used, the OOM-process of the kernel kills digikam. Anyone >> seeing this issue as well? >> >> Regards >> 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 > _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
|
|
In reply to this post by Martin (KDE)
Sound like a packaging problem. Memory leak is not reproducible here.
Gilles Caulier 2013/9/28 Martin (KDE) <[hidden email]>: > Hm > > I tried it with another user on a different computer (same software) and > had no problem to generate the thumbnails. IS there something in the > setup that changes thumbnail behaviour? > > Regards > Martin > > Am 27.09.2013 20:35, schrieb Martin (KDE): >> Hallo >> >> thumbnail regeneration in menu extra->maintainance is a little buggy >> here (recent digikam 3.4 on fedora 19, 64bit). It allocates new memory >> for every photo but never gives the memory back. If all memory (8G) and >> swap (10G) are used, the OOM-process of the kernel kills digikam. Anyone >> seeing this issue as well? >> >> Regards >> 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 Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
|
|
Some even more strange thing: If I run the update for a single album
there is no problem. But as soon as I started the maintainance regeneration, stop it a few pictures later, the album regeneration of thumbnails has the same problems as the maintainance one. Still searching for the reason for this. Martin Am 28.09.2013 16:49, schrieb Gilles Caulier: > Sound like a packaging problem. Memory leak is not reproducible here. > > Gilles Caulier > > 2013/9/28 Martin (KDE) <[hidden email]>: >> Hm >> >> I tried it with another user on a different computer (same software) and >> had no problem to generate the thumbnails. IS there something in the >> setup that changes thumbnail behaviour? >> >> Regards >> Martin >> >> Am 27.09.2013 20:35, schrieb Martin (KDE): >>> Hallo >>> >>> thumbnail regeneration in menu extra->maintainance is a little buggy >>> here (recent digikam 3.4 on fedora 19, 64bit). It allocates new memory >>> for every photo but never gives the memory back. If all memory (8G) and >>> swap (10G) are used, the OOM-process of the kernel kills digikam. Anyone >>> seeing this issue as well? >>> >>> Regards >>> 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 > _______________________________________________ > 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 |
|
|
In reply to this post by Martin (KDE)
Finally I removed my thumbs database (more than 1.2Gig big) and showd
all images in DK (took more than one hour to generate all the thumbs). Point one: thumbs database shrunk to 500M and maintainance thumbs regeneration is fast (almost all thumbs are already there) and no longer leaks memory. I still have no clue what the original problem was/is. Martin Am 27.09.2013 20:35, schrieb Martin (KDE): > Hallo > > thumbnail regeneration in menu extra->maintainance is a little buggy > here (recent digikam 3.4 on fedora 19, 64bit). It allocates new memory > for every photo but never gives the memory back. If all memory (8G) and > swap (10G) are used, the OOM-process of the kernel kills digikam. Anyone > seeing this issue as well? > > Regards > 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 |
«
Return to digikam-users
|
1 view|%1 views
| Free forum by Nabble | Edit this page |