[Digikam-devel] [digikam] [Bug 326525] Severe memory leak during maintainance scan for rebuild thumbnails

[Marcel Wiesweg]

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

--- Comment #28 from Marcel Wiesweg <marcel.wiesweg at gmx.de> ---
Re Memory leak:
Please use a dedicated thumbnail load thread (*) for the catcher. The logic
depends on a enqueue being called after immediately after requesting a
thumbnail, it breaks if the thread receives requests from many places
concurrently so that the "last request" is undefined when calling enqueue. 

Re PGF:
Even if we switch thumbnail creation to another algorithm, we
a) need to continue providing PGF read support for those gigabytes of
thumbnails on our users machines
b) we break backwards compatibility to use a new thumbnail db with an older
version, so it should be done only with a major release

(*)
    ThumbnailLoadThread* thumbnailLoadThread = new ThumbnailLoadThread;
    thumbnailLoadThread->setPixmapRequested(false);
   
thumbnailLoadThread->setThumbnailSize(ThumbnailLoadThread::maximumThumbnailSize());

Note that switching off pixmap generation for this thread also avoids flooding
the cache for the main UI.

-- 
You are receiving this mail because:
You are the assignee for the bug.