| Summary: | When validating a face marker digikam crash | ||
|---|---|---|---|
| Product: | [Applications] digikam | Reporter: | e.longuemare |
| Component: | Faces-Engine | Assignee: | Digikam Developers <digikam-bugs-null> |
| Status: | RESOLVED FIXED | ||
| Severity: | crash | CC: | caulier.gilles, e.longuemare, kurt.wieser |
| Priority: | NOR | Keywords: | drkonqi |
| Version: | 4.0.0 | ||
| Target Milestone: | --- | ||
| Platform: | Ubuntu | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | 5.1.0 | |
| Sentry Crash Report: | |||
| Attachments: |
New crash information added by DrKonqi
screenshot when crash occur screenshot when crash occur New screenshot - Crash when modifying face tag marker - still 4.0.0beta1 |
||
|
Description
e.longuemare
2013-10-24 23:39:39 UTC
Created attachment 83360 [details]
New crash information added by DrKonqi
digikam (4.0.0-beta1) on KDE Platform 4.11.2 using Qt 4.8.2
- What I was doing when the application crashed:
I was building thumbnails with maintenance tools (analyse check) and go to move "bad face marker" - go to one picture view - clic on the tag name - move the marker and clic on OK to validate the change and make the face thumbnail well rotated or/and on the face (The face is sometime well delimited, but it's an other part that is thumb) - This occur on CR2 RAW file with orientation to 8 (270) - after modification thumbnail is the good one.
- Unusual behavior I noticed:
Crash of the digikam main windows (crash and disappear while digikam continue to run)
##LOGS OF DIGIKAM TASK RUNNING##
digikam(26702)/digikam (core) Digikam::DatabaseCoreBackendPrivate::debugOutputFailedTransaction: Failure executing transaction. Error messages:
"QMYSQL: Unable to begin transaction" "MySQL server has gone away" 2006 2
digikam(26702)/digikam (core) Digikam::DatabaseCoreBackend::prepareQuery: Prepare failed!
digikam(26702)/digikam (core) Digikam::DatabaseCoreBackendPrivate::debugOutputFailedQuery: Failure executing query:
"SELECT id, type, modificationDate, orientationHint, data FROM UniqueHashes INNER JOIN Thumbnails ON thumbId = id WHERE uniqueHash=? AND fileSize=?;"
Error messages: "QMYSQL3: Unable to prepare statement" "MySQL server has gone away" 2006 2
Bound values: ()
digikam(26702)/KDCRAW KDcrawIface::KDcraw::loadEmbeddedPreview: Preview data size: 2062575
digikam(26702)/KDCRAW KDcrawIface::KDcraw::loadEmbeddedPreview: Using embedded RAW preview extraction
digikam(26702)/digikam (core) Digikam::DMetadata::getIccProfile: Exif color-space tag is sRGB. Using default sRGB ICC profile.
digikam(26702)/KEXIV2 KExiv2Iface::KExiv2::getImageOrientation: Orientation => Exif.Image.Orientation => 1
digikam(26702)/digikam (core) Digikam::DatabaseCoreBackendPrivate::debugOutputFailedTransaction: Failure executing transaction. Error messages:
"QMYSQL: Unable to begin transaction" "MySQL server has gone away" 2006 2
digikam(26702)/digikam (core) Digikam::DImg::load: "/media/DiskphotosTests/cazedarnes noel 2012/IMG_9545.JPG" : JPEG file identified
digikam(26702)/KEXIV2 KExiv2Iface::KExiv2::getImageOrientation: Orientation => Exif.Image.Orientation => 1
digikam(26702)/digikam (core) Digikam::DatabaseCoreBackendPrivate::debugOutputFailedTransaction: Failure executing transaction. Error messages:
"QMYSQL: Unable to begin transaction" "MySQL server has gone away" 2006 2
digikam(26702)/KDCRAW KDcrawIface::KDcraw::loadEmbeddedPreview: Preview data size: 2254459
digikam(26702)/KDCRAW KDcrawIface::KDcraw::loadEmbeddedPreview: Using embedded RAW preview extraction
digikam(26702)/digikam (core) Digikam::DMetadata::getIccProfile: Exif color-space tag is sRGB. Using default sRGB ICC profile.
digikam(26702)/KEXIV2 KExiv2Iface::KExiv2::getImageOrientation: Orientation => Exif.Image.Orientation => 1
digikam(26702)/digikam (core) Digikam::DatabaseCoreBackendPrivate::debugOutputFailedTransaction: Failure executing transaction. Error messages:
"QMYSQL: Unable to begin transaction" "MySQL server has gone away" 2006 2
digikam(26702)/digikam (core) Digikam::DImg::load: "/media/DiskphotosTests/cazedarnes noel 2012/IMG_9546.JPG" : JPEG file identified
digikam(26702)/KEXIV2 KExiv2Iface::KExiv2::getImageOrientation: Orientation => Exif.Image.Orientation => 1
digikam(26702)/digikam (core) Digikam::DatabaseCoreBackendPrivate::debugOutputFailedTransaction: Failure executing transaction. Error messages:
"QMYSQL: Unable to begin transaction" "MySQL server has gone away" 2006 2
digikam(26702)/KDCRAW KDcrawIface::KDcraw::loadEmbeddedPreview: Preview data size: 1958109
digikam(26702)/KDCRAW KDcrawIface::KDcraw::loadEmbeddedPreview: Using embedded RAW preview extraction
digikam(26702)/digikam (core) Digikam::DMetadata::getIccProfile: Exif color-space tag is sRGB. Using default sRGB ICC profile.
digikam(26702)/KEXIV2 KExiv2Iface::KExiv2::getImageOrientation: Orientation => Exif.Image.Orientation => 1
digikam(26702)/digikam (core) Digikam::DatabaseCoreBackendPrivate::debugOutputFailedTransaction: Failure executing transaction. Error messages:
"QMYSQL: Unable to begin transaction" "MySQL server has gone away" 2006 2
digikam(26702)/digikam (core) Digikam::DatabaseCoreBackend::prepareQuery: Prepare failed!
digikam(26702)/digikam (core) Digikam::DatabaseCoreBackendPrivate::debugOutputFailedQuery: Failure executing query:
"SELECT id, type, modificationDate, orientationHint, data FROM UniqueHashes INNER JOIN Thumbnails ON thumbId = id WHERE uniqueHash=? AND fileSize=?;"
Error messages: "QMYSQL3: Unable to prepare statement" "MySQL server has gone away" 2006 2
Bound values: ()
###END OF LOG###
-- Backtrace (Reduced):
#8 0xb41e71df in __GI_raise (sig=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64
#9 0xb41ea825 in __GI_abort () at abort.c:91
[...]
#11 0xb422eee2 in malloc_printerr (action=<optimized out>, str=<optimized out>, ptr=0x1fc2c5c8) at malloc.c:5018
[...]
#13 0xb65293a8 in QList<QVariant>::node_destruct (this=0x91cbd8c, n=0x16f5c334) at /usr/include/qt4/QtCore/qlist.h:388
#14 0xb6592bd0 in QList<QVariant>::erase (this=0x91cbd8c, afirst=..., alast=...) at /usr/include/qt4/QtCore/qlist.h:811
Sorry, But I think it's related to this https://bugs.kde.org/show_bug.cgi?id=327197. I'm not sure the maintenance as something to do with this as memory usage grow and grow faster when a face marker is modified. The recognition.db grow fast too, from about 20 mo to 35 mo for about ten face markers modified. Thank you, Eric Created attachment 83361 [details]
screenshot when crash occur
Created attachment 83362 [details]
screenshot when crash occur
Digikam conponent : digiKam version 4.0.0-beta1 Codec PGF parallélisé: Non Composant graphique Marble: 0.16.2 (stable version) Demosaic GPL2 pack support: Inconnu Demosaic GPL3 pack support: Inconnu Dématriçage parallélisé: Inconnu Exiv2 peut écrire dans un fichier JP2: Oui Exiv2 peut écrire dans un fichier JPEG: Oui Exiv2 peut écrire dans un fichier PGF: Oui Exiv2 peut écrire dans un fichier PNG: Oui Exiv2 peut écrire dans un fichier TIFF: Oui Exiv2 prend en charge les métadonnées XMP: Oui LibCImg: 130 LibEigen: 3.0.5 LibExiv2: 0.22 LibJPEG: 80 LibJasper: 1.900.1 LibKDE: 4.11.2 LibKExiv2: 2.3.1 LibKGeoMap: 2.0.0 LibKdcraw: 2.4.0 LibLCMS: 2040 LibLensFun: 0.2.7-0 LibPGF: 6.12.27 - bibliothèque interne LibPNG: 1.2.46 LibQt: 4.8.2 LibRaw: 0.15.4 LibTIFF: LIBTIFF, Version 3.9.5 Copyright (c) 1988-1996 Sam Leffler Copyright (c) 1991-1996 Silicon Graphics, Inc. Prise en charge du codec RawSpeed: Inconnu LibGphoto2: 2.4.14 LibKface: 3.0.0 LibKipi: 2.1.0 LibOpenCV: 2.4.5 Modules externes KIPI: 3.5.0 Moteur de base de données: QMYSQL Serveur interne de base de données: Non Digikam version : Date de compilation : Nov 5 2013 (cible : debugfull) Rév. : ea2847ec161df82f8d64e70afdbc5d12feb7708e kde : Platform Version 4.11.2 digiKam 4.0.0 is out : http://www.digikam.org/node/713 Please check if this entry still valid with this new version. Thanks in advance Gilles Caulier Hello,
I have tried now to reproduce it with the same version as previous message : 4.0.0 beta1 to be sure, and it still crash.
Only one digikam componant has change (update) :
digiKam version 4.0.0-beta1
LibKDE: 4.13.0
Date de compilation : Nov 5 2013 (cible : debugfull)
Rév. : ea2847ec161df82f8d64e70afdbc5d12feb7708e
It's a memory leak, I have more info :
digikam(17281)/digikam (core) Digikam::DMetadata::getImageHistory: Loading image history ""
digikam(17281)/KEXIV2 KExiv2Iface::KExiv2::getImageDateTime: DateTime => Exif.Photo.DateTimeOriginal => QDateTime("jeu. déc. 27 01:00:39 2012")
digikam(17281)/digikam (core) Digikam::DImg::load: "/media/DiskphotosTests/noel 2011 beziers/PICT0223.JPG" : JPEG file identified
digikam(17281)/KEXIV2 KExiv2Iface::KExiv2::getImageOrientation: Orientation => Exif.Image.Orientation => 1
digikam(17281)/digikam (core) Digikam::DMetadata::getIccProfile: Exif color-space tag is sRGB. Using default sRGB ICC profile.
digikam(17281)/digikam (core) Digikam::DImg::load: "/media/DiskphotosTests/noel 2011 beziers/PICT0219.JPG" : JPEG file identified
digikam(17281)/KEXIV2 KExiv2Iface::KExiv2::getImageOrientation: Orientation => Exif.Image.Orientation => 1
digikam(17281)/KEXIV2 KExiv2Iface::KExiv2::getImageOrientation: Orientation => Exif.Image.Orientation => 1
digikam(17281)/digikam (core) Digikam::DImg::load: "/media/DiskphotosTests/noel 2011 beziers/PICT0217.JPG" : JPEG file identified
digikam(17281)/KEXIV2 KExiv2Iface::KExiv2::getImageOrientation: Orientation => Exif.Image.Orientation => 1
digikam(17281)/digikam (core) Digikam::DImg::load: "/media/DiskphotosTests/noel 2011 beziers/PICT0216.JPG" : JPEG file identified
digikam(17281)/KEXIV2 KExiv2Iface::KExiv2::getImageOrientation: Orientation => Exif.Image.Orientation => 1
digikam(17281)/digikam (core) Digikam::FaceUtils::identityForTag: Found kface identity 8 for tag 38
digikam(17281)/KFACE KFaceIface::trainIdentityBatch: Training 1 images for identity 8
OpenCV Error: Insufficient memory (Failed to allocate 65540 bytes) in OutOfMemoryError, file /home/eric/opencv-2-4-5-SH/OpenCV/opencv-2.4.5/modules/core/src/alloc.cpp, line 52
digikam(17281)/KFACE: cv::Exception training LBPH: /home/eric/opencv-2-4-5-SH/OpenCV/opencv-2.4.5/modules/core/src/alloc.cpp:52: error: (-4) Failed to allocate 65540 bytes in function OutOfMemoryError
digikam(17281)/digikam (core) Digikam::FacePipeline::Private::checkFinished: Check for finish: 0 packages, 0 infos to filter, hasFinished() true
I will try tomorrow with digikam 4.0.0 release.
Thank you,
Eric
Created attachment 86822 [details]
New screenshot - Crash when modifying face tag marker - still 4.0.0beta1
Move a face tag marker : fullfill memory and crash
Git commit fa909aa96e7e41225551cd9e866618717f1ea546 by Gilles Caulier. Committed on 11/06/2014 at 21:06. Pushed by cgilles into branch 'master'. use a better C++ exception wrapper to handle non OpenCV exceptions (as pure C++ one) Related: bug 335624, bug 330342, bug 329873, bug 326742, bug 326585, bug 324774, bug 323888, bug 323361, bug 320812, bug 312440, bug 309027, bug 308645, bug 301611, bug 297558, bug 285517 M +4 -0 libkface/facedetector.cpp M +17 -2 libkface/recognitiondatabase.cpp http://commits.kde.org/libkface/fa909aa96e7e41225551cd9e866618717f1ea546 With next digiKam 4.1.0, i fixed libkface to handle all C++ exception (and not only OpenCV exception). So, at least, digiKam must crash lesser now. If you want to review this entry again, use current implementation from git/master, or wait next 4.1.0 release... Thanks to update your feedback Gilles Caulier Git commit 4662dd94102f8144bc65ce1cb66d6b6cb1d500fd by Gilles Caulier. Committed on 18/06/2014 at 14:22. Pushed by cgilles into branch 'master'. Libkface now depand of last stable OpenCV library version 2.4.9 This prevent internal crash int Cv:Algorithm that we cannot handle in libkface as exception. Now, Face Recognition do not crash but still report Exception at training operations, especially about wrong Cv:Matrix size : digikam(8673)/digikam (core) Digikam::DImg::load:"/mnt/data2/photos/GILLES/NEW/Adrien/2010-04-13/20100413_009.jpg" : JPEG file identified OpenCV Error: Assertion failed (0 <= _dims && _dims <= CV_MAX_DIM) in setSize, file /mnt/devel/opencv/modules/core/src/matrix.cpp, line 89 digikam(8673)/KFACE: cv::Exception training LBPH: /mnt/devel/opencv/modules/core/src/matrix.cpp:89: error: (-215) 0 <=_dims && _dims <= CV_MAX_DIM in function setSize It still a problem somwhere, but it's better than previous state. Related: bug 335624, bug 330342, bug 329873, bug 326742, bug 326585, bug 324774, bug 323888, bug 323361, bug 320812, bug 312440, bug 309027, bug 308645, bug 301611, bug 297558, bug 285517 M +1 -1 CMakeLists.txt http://commits.kde.org/libkface/4662dd94102f8144bc65ce1cb66d6b6cb1d500fd Git commit 1fff86f31e3bf47a2a2cfa6eaa98bb1bdf1a863b by Gilles Caulier. Committed on 24/06/2014 at 12:32. Pushed by cgilles into branch 'master'. add more test before to commit/checkout compressed histogram data in Face database, to prevent crashes, especially if data are corrupted from database. Related: bug 335624, bug 330342, bug 329873, bug 326742, bug 326585, bug 324774, bug 323888, bug 320812, bug 312440, bug 309027, bug 308645, bug 301611, bug 297558, bug 285517 M +62 -28 libkface/database/trainingdb.cpp http://commits.kde.org/libkface/1fff86f31e3bf47a2a2cfa6eaa98bb1bdf1a863b With next digiKam 4.1.0, a lots of improvements/fixes have be done around face management. Please give us a fresh feedback. Note i recommend to delete face recognition database to prevent dysfunction due to possible wrong data store in this container. Look where file is located in my computer : [gilles@localhost database]$ pwd /home/gilles/.kde4/share/apps/libkface/database [gilles@localhost database]$ ls -al total 397028 drwx------ 2 gilles gilles 4096 juin 24 14:22 ./ drwx------ 3 gilles gilles 4096 juin 18 19:08 ../ -rw-r--r-- 1 gilles gilles 406543360 juin 24 14:22 recognition.db [gilles@localhost database]$ *** Bug 337936 has been marked as a duplicate of this bug. *** We need a fresh feedback about this file using last digiKam 4.2.0 Gilles Caulier New digiKam 4.11.0 is available : https://www.digikam.org/node/740 Can you reproduce the problem with this release ? Gilles Caulier digiKam 4.12.0 is out : https://www.digikam.org/node/741 We need a fresh feedback using this release please... Thanks in advance. Gilles Caulier With next 5.1.0 release, a lots of investigations have be done around OpenCV face module integration with digiKam Face Engine. See bug #365202 history for details. I close this file now. Don't hesistate to re-open if necessary. Gilles Caulier |