Running maintenance -> image quality sorter leaks memory.
When running on my collection it leaked few MB/sec up to around 7G (around 6-7% of my collection according to progress bar) when I stopped it. Had to exit digikam to release it.
Steps to Reproduce:
1. Run Maintenance -> Image Quality Sorter
Memory usage grows around few MB/sec
It is not released until exiting digikam
Memory usage stays flat, any extra memory allocated during quality sorting is released after this process ends.
*** This bug has been marked as a duplicate of bug 330230 ***
Git commit 6a9fd9891a3ff341dc42fe36158cbf0101d513b6 by Maik Qualmann.
Committed on 17/12/2017 at 19:20.
Pushed by mqualmann into branch 'master'.
delete threads from memory when they are finished
Related: bug 375317, bug 375035, bug 321784, bug 325712, bug 328732, bug 331912, bug 344661, bug 345395, bug 350549, bug 381877, bug 338249, bug 329651, bug 329091, bug 387821, bug 381222
M +2 -1 NEWS
M +25 -0 libs/database/dbjobs/dbjobsmanager.cpp
M +35 -0 libs/iojobs/iojobsmanager.cpp
Following this commit:
... the approach to fix this problem is under way and new digiKam 5.8.0 pre-release bundles will be compiled tonight to lets a chance to end-users to give a feedback about this fix before the 5.8.0 official release planed before Christmas 2017.
The bundles will be available in 2 hours at this url:
Please do not waste time to test if this file is always valid for next 5.8.0.
Thanks in advance
Not reproducible with 7.0.0-beta1