Bug 345395 - Face Management the Memory and Swap growed to max
Summary: Face Management the Memory and Swap growed to max
Alias: None
Product: digikam
Classification: Applications
Component: Faces-Engine (show other bugs)
Version: 4.8.0
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: Digikam Developers
Depends on:
Reported: 2015-03-21 14:38 UTC by hans.freiberger
Modified: 2019-12-23 07:46 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In: 7.0.0

Face Management, Memory and Swap growed (105.42 KB, image/jpeg)
2015-03-21 14:42 UTC, hans.freiberger

Note You need to log in before you can comment on or make changes to this bug.
Description hans.freiberger 2015-03-21 14:38:36 UTC
In Face Management the Memory and Swap growed to max. There is 4 / 6 GB. By the reached max: Crash! It's even picture to set Face.

Reproducible: Always

Steps to Reproduce:
1. Set the Face Management at one picture
2. then no more input action 
3. the Memory and swap go to max in the next seconds
4. Crash
Comment 1 hans.freiberger 2015-03-21 14:42:54 UTC
Created attachment 91664 [details]
Face Management, Memory and Swap growed

it is a snapshot from set Face Mask to crash
Comment 2 caulier.gilles 2015-03-21 14:43:32 UTC

*** This bug has been marked as a duplicate of bug 338176 ***
Comment 3 Maik Qualmann 2017-12-17 19:21:34 UTC
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 330227, bug 331912, bug 344661, 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

Comment 4 caulier.gilles 2017-12-17 20:02:27 UTC
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

Gilles Caulier
Comment 5 caulier.gilles 2019-12-23 07:46:25 UTC
Problem is fixed with new 7.0.0-beta1 through this long story from this bug


You can test digiKam 7.0.0-beta1 with bundle available here:


Don't hesitate to give us a fresh feedback about his entry.

Thanks in advance

Gilles Caulier