Bug 351016 - Crash in Windows when building finger-prints
Summary: Crash in Windows when building finger-prints
Status: RESOLVED WORKSFORME
Alias: None
Product: digikam
Classification: Applications
Component: Searches-Similarity (show other bugs)
Version: 4.11.0
Platform: Microsoft Windows Microsoft Windows
: NOR crash
Target Milestone: ---
Assignee: Digikam Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-08-05 20:41 UTC by bsteer
Modified: 2016-07-07 21:50 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In: 5.0.0
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description bsteer 2015-08-05 20:41:04 UTC
Application: digikam (4.11.0)
KDE Platform Version: 4.10.2
Qt Version: 4.8.4
Operating System: WindowsNT Windows 6.2 i686

-- Information about the crash:
digiKam crashes when trying to build finger-prints. First encountered when trying out "Fuzzy" menu for first time and getting prompt to do this. Confirmed to be repeatable when trying to build finger-print either via this prompt or via the Tools->Maintenance menu. It appears to run OK for a minute or wo before crashing. I no longer get the prompt on the Fuzzy menu but it still crashes when choosing the Rebuild Finger-prints option in the Maintenance menu.

The crash can be reproduced every time.

-- Backtrace:
Application: digiKam (digikam.exe), signal: EXCEPTION_ACCESS_VIOLATION


ntdll.dll!ZwWaitForSingleObject() [[unknown] @ -1] at 0x772cc4bc
KERNELBASE.dll!WaitForSingleObject() [[unknown] @ -1] at 0x76382c02
QtCore4.dll!QMutex::lockInternal() [[unknown] @ -1] at 0x7745402e
ntdll.dll!RtlAllocateHeap() [[unknown] @ -1] at 0x772d10e9
QtCore4.dll!QCoreApplication::postEvent() [[unknown] @ -1] at 0x77540a38
QtCore4.dll!QMetaObject::connectSlotsByName() [[unknown] @ -1] at 0x775547aa
QtCore4.dll!QMetaObject::connectSlotsByName() [[unknown] @ -1] at 0x775547ba
QtCore4.dll!QMetaObject::activate() [[unknown] @ -1] at 0x775549ba
QtCore4.dll!QObject::~QObject() [[unknown] @ -1] at 0x775506d9
digikamlib.dll!Digikam::IccManager::setObserver() [[unknown] @ -1] at 0x77cabae9
digikamlib.dll!Digikam::IccManager::setObserver() [[unknown] @ -1] at 0x77db7a1a
digikamlib.dll!Digikam::IccManager::setObserver() [[unknown] @ -1] at 0x77db7a97
ntdll.dll!RtlInitializeCriticalSection() [[unknown] @ -1] at 0x772d97de
ntdll.dll!RtlInitializeCriticalSection() [[unknown] @ -1] at 0x772d9758
ntdll.dll!RtlReportSilentProcessExit() [[unknown] @ -1] at 0x772fcd68
ntdll.dll!RtlExitUserProcess() [[unknown] @ -1] at 0x772fce11
KERNEL32.DLL!ExitProcess() [[unknown] @ -1] at 0x77099863
MSVCR100.dll!_query_new_mode() [[unknown] @ -1] at 0x8c7997
MSVCR100.dll!_query_new_mode() [[unknown] @ -1] at 0x8c7ab0
MSVCR100.dll!exit() [[unknown] @ -1] at 0x8fbf47
kdeui.dll!QList<KSortableItem<QString,int> >::value() [[unknown] @ -1] at 0xfadf7ef

Report to https://bugs.kde.org/

Reproducible: Always

Steps to Reproduce:
1. Open digiKam
2. Tools->Maintenance->Rebuild Finger-prints
3.Crash



Unable to submit via Crash Reporting Assistant.
"Error sending the crash report: /Received unexpected error code 410 from bugzilla. Error"
Comment 1 caulier.gilles 2016-06-09 15:38:28 UTC
New digiKam 5.0.0-beta7 installer for Windows is available for testing :

https://drive.google.com/open?id=0B7yq-xFihT0_SzhxVzF1RDhPbFE

Please report if problem remain with this version.

Thanks in advance

Gilles Caulier
Comment 2 caulier.gilles 2016-06-12 18:24:17 UTC
With the last 5.0.0-beta7 for Windows, i scanned a collection of images 5000 images shared through the network (RAW, JPEG, PNG, TIFF? AVI, MKV, MPG, etc), and the dysfunction is not reproducible.

I close this file now as workforme with 5.0.0. Don't hesitate to re-open if necessary.

Gilles Caulier