[Digikam-devel] [digikam] [Bug 338176] Digikam-4.2.0 sometimes crashes when recognising faces

[Christian]

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

--- Comment #4 from Christian <gentoo at moin.fi> ---
This is the top of the Valgrind information, by the way... afterwards, the
program will continue running about another 50 minutes or so until it runs out
of swap space again, and then valgrind crashes with the long error message that
was truncated (see previous post).


ca at puolukka ~ $ valgrind --tool=memcheck --leak-check=full --error-limit=no
digikam
==32147== Memcheck, a memory error detector
==32147== Copyright (C) 2002-2013, and GNU GPL'd, by Julian Seward et al.
==32147== Using Valgrind-3.9.0 and LibVEX; rerun with -h for copyright info
==32147== Command: digikam
==32147== 
Object::connect: No such signal org::freedesktop::UPower::DeviceAdded(QString)
Object::connect: No such signal
org::freedesktop::UPower::DeviceRemoved(QString)
QSqlDatabasePrivate::removeDatabase: connection 'ConnectionTest' is still in
use, all queries will cease to work.
==32147== Warning: set address range perms: large range [0x14e4ff040,
0x1f4e38020) (undefined)
OpenCV Error: Insufficient memory (Failed to allocate 262144 bytes) in
OutOfMemoryError, file
/portage_builddir/portage/media-libs/opencv-2.4.5/work/opencv-2.4.5/modules/core/src/alloc.cpp,
line 52
==32147== Warning: set address range perms: large range [0x14e4ff028,
0x1f4e38038) (noaccess)


Notes on timing:
The lines up to "Qsql" all appear while the startup window is still showing.
When I start the face recognition, the progress bar slowly climbs to 11% (slow
because of Valgrind). Then memory is filled up, maybe to 7GB or so (using some
swap), at which point the first warning is shown. There are no "problems" yet
at this point, the program continues running and after a while memory use
actually goes down. Then memory use increases again up to hitting the swap
limit. This causes the OpenCV error message to appear. Progress bar is still at
11%, but goes up to 13% after these OpenCV error messages. Then memory fills up
again slowly up to the limit, which causes Valgrind to crash and produce the
long output, which I reported in the previous post.

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