[digikam] [Bug 329091] MySQL : needs to set "max-allowed-packet" server settings from 4.096 to 16.777.216 to prevent Maintenance tool crash

Sat Aug 13 09:12:39 BST 2016

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

--- Comment #33 from uwe.haider at gmx.net ---
Tested now with gdb and digikam-5.1.0 (with german trasnlation!):
New crash with face-search - sorry no backtrace:

------------
digikam.general: Check for finish:  51 packages, 0 infos to filter,
hasFinished() false

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7ffecdffb700 (LWP 11679)]
operator== (s1=..., s2=...) at tools/qstring.cpp:2686
2686    tools/qstring.cpp: Datei oder Verzeichnis nicht gefunden.

-----------------
The multicore-option was NOT set. But I found this in gdb-Output:
------
digikam.general: Using  4  CPU core to run threads
[New Thread 0x7ffee7ff7700 (LWP 32609)]
digikam.general: Action Thread run  1  new jobs
digikam.database: " ( ( (ImageTagProperties.tagid=? OR ImageTagProperties.tagid
IN (SELECT id FROM TagsTree WHERE pid=?)) AND ImageTagProperties.property=?  )
OR ( (ImageTagProperties.tagid=? OR ImageTagProperties.tagid IN (SELECT id FROM
TagsTree WHERE pid=?)) AND ImageTagProperties.property=?  ) ) "
digikam.database: Search query:
 "SELECT DISTINCT Images.id, Images.name, Images.album,       
Albums.albumRoot,        ImageInformation.rating, Images.category,       
ImageInformation.format, ImageInformation.creationDate,       
Images.modificationDate, Images.fileSize,        ImageInformation.width, 
ImageInformation.height,        ImageTagProperties.value,
ImageTagProperties.property, ImageTagProperties.tagid  FROM Images        INNER
JOIN ImageTagProperties ON ImageTagProperties.imageid=Images.id        LEFT
JOIN ImageInformation ON Images.id=ImageInformation.imageid        INNER JOIN
Albums           ON Albums.id=Images.album WHERE Images.status=1 AND (  ( (
(ImageTagProperties.tagid=? OR ImageTagProperties.tagid IN (SELECT id FROM
TagsTree WHERE pid=?)) AND ImageTagProperties.property=?  ) OR (
(ImageTagProperties.tagid=? OR ImageTagProperties.tagid IN (SELECT id FROM
TagsTree WHERE pid=?)) AND ImageTagProperties.property=?  ) )  );" 
 (QVariant(int, 1111), QVariant(int, 1111), QVariant(QString,
"autodetectedFace"), QVariant(int, 1111), QVariant(int, 1111),
QVariant(QString, "tagRegion"))
-------

digikam uses 4 cores, maintenance not??

This are the used components:
digikam version 5.1.0
CPU cores: 4
Eigen: 3.2.8
Exiv2: 0.25
Exiv2 can write to Jp2: Ja (yes)
Exiv2 can write to Jpeg: Ja (yes)
Exiv2 can write to Pgf: Ja (yes)
Exiv2 can write to Png: Ja (yes)
Exiv2 can write to Tiff: Ja (yes)
Exiv2 supports XMP metadata: Ja (yes)
KDE: 5.25.0
LensFun: 0.3.2-0
LibCImg: 130
LibJPEG: 62
LibJasper: 1.900.1
LibLCMS: 2060
LibLqr support: Ja (yes)
LibPGF: 7.15.32
LibPNG: 1.6.21+apng
LibRaw: 0.18.0-201604
LibTIFF: LIBTIFF, Version 4.0.6 Copyright (c) 1988-1996 Sam Leffler Copyright
(c) 1991-1996 Silicon Graphics, Inc.
Marble: 0.24.1 (stable release)
Parallelized demosaicing: Ja (yes)
Qt: 5.6.1
RawSpeed codec support: Keine (no)
DBus support: Ja  (yes)
Datenbanktreiber: QMYSQL
Interner Datenbank-Server:: Keine (no)
KIPI-Module: 5.1.0
LibGphoto2: 2.5.10
LibKipi: 5.1.0
LibOpenCV: 3.1.0
Unterstützung für Baloo: Ja (yes)
Unterstützung für Calender: Nein (no)
Unterstützung für Panorama: Ja  (yes)
Unterstützung für QtMultimedia: Ja (yes)
Unterstützung von Akonadi-Kontakten: Nein (no)

Your question for multicore functionality in exiv2: firefly has searched the
source-code for fork or threads and hasn't found something like this. This
output is gdb-output using only one core for maintenacce (face-detection only):
------------
digikam.general: Use Exif/IPTC preview extraction. Size of image:  1280 x 851
digikam.metaengine: Orientation => Exif.Image.Orientation =>  1
digikam.facesengine: detectMultiScale gave  ()
digikam.general: Found 0 faces in "20141017T143010.png" QSize(3264, 4928)
QSize(3264, 4928)
digikam.general: Use Exif/IPTC preview extraction. Size of image:  1280 x 851
digikam.general: Check for finish:  51 packages, 0 infos to filter,
hasFinished() false
digikam.metaengine: Orientation => Exif.Image.Orientation =>  1
digikam.general: Use Exif/IPTC preview extraction. Size of image:  1280 x 851
digikam.metaengine: Orientation => Exif.Image.Orientation =>  1
digikam.general: Use Exif/IPTC preview extraction. Size of image:  1280 x 851
digikam.metaengine: Orientation => Exif.Image.Orientation =>  1
digikam.general: Use Exif/IPTC preview extraction. Size of image:  1280 x 851
digikam.metaengine: Orientation => Exif.Image.Orientation =>  1
digikam.metaengine: Orientation => Exif.Image.Orientation =>  6
digikam.general: Use Exif/IPTC preview extraction. Size of image:  1280 x 851
digikam.metaengine: Orientation => Exif.Image.Orientation =>  1
digikam.general: Use Exif/IPTC preview extraction. Size of image:  1280 x 851
digikam.metaengine: Orientation => Exif.Image.Orientation =>  1
digikam.dimg: "/home/uhai/Dokumente/CFotobuch/Carla 18/Kopie von
SabineHaider2006-06-22_10-16-46D50.JPG"  : JPEG file identified
digikam.metaengine: Orientation => Exif.Image.Orientation =>  1
digikam.dimg: "/home/uhai/Bilder_alt/2014/2014-10-17/20141017T143011_v1.png"  :
PNG file identified
digikam.dimg: "/home/uhai/Dokumente/CFotobuch/Carla 18/Kopie von
SabineHaider2006-06-22_10-16-46D50.JPG"  : JPEG file identified
[Switching to Thread 0x7ffee7ff7700 (LWP 6946)]
Catchpoint 1 (exception thrown), __cxxabiv1::__cxa_throw (obj=0x7ffeec27dd40,
tinfo=0x7ffff71a8340 <typeinfo for Exiv2::BasicError<char>>,
dest=0x7ffff6818ce0 <Exiv2::BasicError<char>::~BasicError()>)
    at
/var/tmp/portage/sys-devel/gcc-4.9.3/work/gcc-4.9.3/libstdc++-v3/libsupc++/eh_throw.cc:63
63      in
/var/tmp/portage/sys-devel/gcc-4.9.3/work/gcc-4.9.3/libstdc++-v3/libsupc++/eh_throw.cc
--------
seems the "exiv2"-break appears with even one core....

Hope it helps. If you need more infos, don't hesitate to ask. I'm glad to
help....

uhai

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