[Digikam-devel] [digikam] [Bug 317413] digiKam crashed while tagging faces

[Michal Sylwester]

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

--- Comment #17 from Michal Sylwester <msylwester at gmail.com> ---
Thanks for the tip, I tried the git version, and it's better, but...
Until tagging first face CPU usage is minimal, memory usage is about 300M with
my collection.
After tagging first face:
- one thread starts working (I guess updating the recognition DB with data from
newly tagged face), which seems IO bound
- Memory usage grows very quickly to about 6G
- Just closing digikam window does not stop several threads (including the
worker mentioned above) from finishing

Tagging more faces does not change anything.
This is still too resource hungry for me, but better than before.

It seems this time code loops in (or at least I haven't seen it leave)
KFaceIface::TrainingDB::updateLBPHFaceModel method: 
#0  KFaceIface::TrainingDB::updateLBPHFaceModel (this=0x3350850, model=...) at
/home/msylw/devel/digikam/dk/extra/libkface/libkface/database/trainingdb.cpp:232
#1  0x00007f6b87f65213 in KFaceIface::OpenCVLBPHFaceRecognizer::train
(this=0x7f6b24060910, images=..., labels=..., context=...)
    at
/home/msylw/devel/digikam/dk/extra/libkface/libkface/recognition-opencv-lbph/opencvlbphfacerecognizer.cpp:173
#2  0x00007f6b87f83b89 in
KFaceIface::trainIdentityBatch<KFaceIface::OpenCVLBPHFaceRecognizer>
(r=0x7f6b24060910, identitiesToBeTrained=..., data=0x7f6b2aff43b0,
trainingContext=..., d=0x33501e0)
    at
/home/msylw/devel/digikam/dk/extra/libkface/libkface/recognitiondatabase.cpp:704
#3  0x00007f6b87f830d5 in KFaceIface::RecognitionDatabase::Private::train
(this=0x33501e0, r=0x7f6b24060910, identitiesToBeTrained=...,
data=0x7f6b2aff43b0, trainingContext=...)
    at
/home/msylw/devel/digikam/dk/extra/libkface/libkface/recognitiondatabase.cpp:727
#4  0x00007f6b87f83189 in KFaceIface::RecognitionDatabase::train
(this=0x334f4e8, identitiesToBeTrained=..., data=0x7f6b2aff43b0,
trainingContext=...)
    at
/home/msylw/devel/digikam/dk/extra/libkface/libkface/recognitiondatabase.cpp:738
#5  0x000000000071d42d in Digikam::Trainer::process (this=0x334f4d0,
package=...) at
/home/msylw/devel/digikam/dk/core/utilities/facemanagement/facepipeline.cpp:1030
#6  0x000000000071652b in Digikam::Trainer::qt_static_metacall (_o=0x334f4d0,
_c=QMetaObject::InvokeMetaMethod, _id=1, _a=0x7f6b04100860) at
/home/msylw/devel/digikam/dk/build/core/digikam/facepipeline_p.moc:580
#7  0x00007f6b839c0dce in QObject::event (this=0x334f4d0, e=<optimized out>) at
kernel/qobject.cpp:1194
#8  0x00007f6b870d1a9f in Digikam::WorkerObject::event (this=0x334f4d0,
e=0x7f6b04110b70) at
/home/msylw/devel/digikam/dk/core/libs/threads/workerobject.cpp:160
#9  0x00007f6b84399dfc in QApplicationPrivate::notify_helper
(this=this at entry=0x2b21190, receiver=receiver at entry=0x334f4d0,
e=e at entry=0x7f6b04110b70) at kernel/qapplication.cpp:4567
#10 0x00007f6b843a0470 in QApplication::notify (this=this at entry=0x7fffbf01f350,
receiver=receiver at entry=0x334f4d0, e=e at entry=0x7f6b04110b70) at
kernel/qapplication.cpp:4353
#11 0x00007f6b850a3c6a in KApplication::notify (this=0x7fffbf01f350,
receiver=0x334f4d0, event=0x7f6b04110b70) at
../../kdeui/kernel/kapplication.cpp:311
#12 0x00007f6b839a88bd in QCoreApplication::notifyInternal
(this=0x7fffbf01f350, receiver=receiver at entry=0x334f4d0,
event=event at entry=0x7f6b04110b70) at kernel/qcoreapplication.cpp:946
#13 0x00007f6b839abe1f in sendEvent (event=0x7f6b04110b70, receiver=0x334f4d0)
at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:231

Looks different from before, so something seems to be indeed fixed :)

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