| Summary: | Face tagging has massive memory leak | ||
|---|---|---|---|
| Product: | [Applications] digikam | Reporter: | René Fritz <rf-kde> |
| Component: | Faces-Engine | Assignee: | Digikam Developers <digikam-bugs-null> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | caulier.gilles, christian.gottschall, nf, ogni |
| Priority: | NOR | ||
| Version: | 3.4.0 | ||
| Target Milestone: | --- | ||
| Platform: | Compiled Sources | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | 7.0.0 | |
| Sentry Crash Report: | |||
| Attachments: | memory graph with comments | ||
|
Description
René Fritz
2013-10-06 17:44:09 UTC
Created attachment 82691 [details]
memory graph with comments
Additional information: You can not end digikam when this happens. The gui disapears, but the process ist still running and eats memory. sigterm ends digikam. Just tested 3.4 kubuntu packages. The same problem. *** Bug 329164 has been marked as a duplicate of this bug. *** I am facing the same issue, running openSuSE Tumbleweed with Kernel 3.12 and KDE 4.11.3. The face recognition requires a lot of memory in general and there is no switch or so to limit it. As the guys before me wrote Digicam will eat up all available memory even swap. I upgraded my system today to 16GB RAM plus 120GB SSD swap. When working with face recognition for 5000 pictures is it just a matter of memory bandwith until Digikam allocated more than 40GB of memory. Read, write and delete to RAM continues but no progress in operation can be detected. For me it stay in status "Applying face changes" for hours when I made changes to 100-200 pictures. I have the same Issue in digiKam 3.4.0 on Kubuntu 13.10 KDE 4.11.3 *** This bug has been marked as a duplicate of bug 323888 *** 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 328732, bug 330227, 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 https://commits.kde.org/digikam/6a9fd9891a3ff341dc42fe36158cbf0101d513b6 Following this commit: https://commits.kde.org/digikam/6a9fd9891a3ff341dc42fe36158cbf0101d513b6 ... 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: https://files.kde.org/digikam/ Please do not waste time to test if this file is always valid for next 5.8.0. Thanks in advance Gilles Caulier Problem is fixed with new 7.0.0-beta1 through this long story from this bug https://bugs.kde.org/show_bug.cgi?id=399923 You can test digiKam 7.0.0-beta1 with bundle available here: https://download.kde.org/unstable/digikam/ Don't hesitate to give us a fresh feedback about his entry. Thanks in advance Gilles Caulier |