Bug 314235 - Crash on startup
Summary: Crash on startup
Status: RESOLVED FIXED
Alias: None
Product: digikam
Classification: Applications
Component: Database-Scan (show other bugs)
Version: 3.0.0
Platform: Microsoft Windows Microsoft Windows
: NOR crash
Target Milestone: ---
Assignee: Digikam Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-02-01 06:09 UTC by Andrey
Modified: 2016-07-09 15:55 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In: 5.1.0


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Andrey 2013-02-01 06:09:59 UTC
Application: digikam (3.0.0-rc)
KDE Platform Version: 4.8.5 (4.8.5)
Qt Version: 4.8.2
Operating System: WindowsNT Windows 7 i686

-- Information about the crash:
- What I was doing when the application crashed:
Just installed it on Win7 x64 (I have admin rights). In the initial wizard I only changed default directory of picture library and digiKam database to F:\Pictures . This folder contains subfolders (one sub-folder with space in the name) about 5-6 levels deep with general year/year_month_day structure. Whole F:/Pictures contains about 10k images

- Custom settings of the application:

Other than pictures library, Everything was default

The crash can be reproduced every time.

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


ntdll.dll!ZwWaitForSingleObject() [[unknown] @ -1] at 0x772af8b1
kernel32.dll!WaitForSingleObjectEx() [[unknown] @ -1] at 0x76651194
kernel32.dll!WaitForSingleObject() [[unknown] @ -1] at 0x76651148
QtCore4.dll!QWaitCondition::wait() [[unknown] @ -1] at 0x6b81855b
digikamlib.dll!Digikam::PGFSettings::getCompressionValue() [[unknown] @ -1] at 0x635b5f60
digikamlib.dll!Digikam::PGFSettings::getCompressionValue() [[unknown] @ -1] at 0x635b609a
digikamlib.dll!Digikam::PGFSettings::getCompressionValue() [[unknown] @ -1] at 0x635830df

Reported using DrKonqi
Comment 1 caulier.gilles 2013-02-01 06:44:00 UTC
Sound like it crash into PGF library...

Gilles Caulier
Comment 2 Ananta Palani 2013-06-10 14:17:16 UTC
(In reply to comment #0)

Hi Andrey,

Could you try just released digiKam 3.1.0 and see if the problem is still there? The new version how folders and images are watched in the OS which may fix your problem. Here is a link to the installer:
   http://download.kde.org/stable/digikam/digiKam-installer-3.1.0-win32.exe
Comment 3 caulier.gilles 2013-11-08 15:00:12 UTC
We need a suitable backtrace to fix the problem... Look here for details ;

http://techbase.kde.org/Development/Tutorials/Debugging/Debugging_on_MS_Windows

Gilles Caulier
Comment 4 caulier.gilles 2015-06-30 08:07:54 UTC
New digiKam 4.11.0 is available :

https://www.digikam.org/node/740

Can you reproduce the problem with this release ?
Comment 5 caulier.gilles 2015-07-06 07:40:27 UTC
digiKam 4.11.0 Windows installer is available for download :

http://download.kde.org/stable/digikam/digiKam-installer-4.11.0-win32.exe.mirrorlist
Comment 6 caulier.gilles 2015-08-20 06:52:08 UTC
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
Comment 7 caulier.gilles 2016-07-09 15:54:07 UTC
This problem is not reproducible with last 5.0.0.
I close this file now. Don't hesitate to re-open it if necessary.
Gilles Caulier