https://bugs.kde.org/show_bug.cgi?id=376891
--- Comment #3 from bzru...@protonmail.ch --- (In reply to caulier.gilles from comment #1) > Where digiKam waste time at startup ? Can you investigate using kcallgrind > tool ? This will indicate which code will be called a lots of time in this > situation... > > Gilles Caulier Hi Gilles, Digikam starts within a minute or two, so that is no problem for me as I usually will start it once a day. The problem comes up when I try to add/edit/delete a tag, Digikam will freeze for a whole minute until done. I just installed valgrind and started digikam like this: valgrind --tool=callgrind digikam I get lots of segment overflows like : ==5290== brk segment overflow in thread #1: can't grow to 0x4a38000 and I am waiting now 20 minutes for Digikam to start up ;) I found some info on stackoverflow: http://stackoverflow.com/questions/35129135/valgrind-reporting-a-segment-overflow still not sure if that is a problem at all. However, seems I can't even get Digikam to start up running valgrind. I killed the process and attaching the output till here, maybe it's already usefull for debugging. Thanks! -- You are receiving this mail because: You are watching all bug changes.