| Summary: | digiKam crashes when importing photos from HD | ||
|---|---|---|---|
| Product: | [Applications] digikam | Reporter: | Rudolf Rezucha <rudolpho.rundablage> |
| Component: | Import-Albums | Assignee: | Digikam Developers <digikam-bugs-null> |
| Status: | RESOLVED FIXED | ||
| Severity: | crash | CC: | caulier.gilles, metzpinguin |
| Priority: | NOR | ||
| Version First Reported In: | 7.3.0 | ||
| Target Milestone: | --- | ||
| Platform: | Microsoft Windows | ||
| OS: | Microsoft Windows | ||
| Latest Commit: | Version Fixed/Implemented In: | 7.4.0 | |
| Sentry Crash Report: | |||
| Attachments: |
Systeminfo for my PC
digiKam Trace Log because digiKam no longer reacts |
||
|
Description
Rudolf Rezucha
2021-10-23 04:18:49 UTC
Please follow instructions under Windows to capture the digiKam debug traces with DebugView tool: https://www.digikam.org/contribute/ Don't forget to setup right Windows environment variable and run DebugView before digiKam. Try to reproduce the dysfunction, and post the captured traces here. Gilles Caulier Created attachment 142782 [details]
Systeminfo for my PC
Created attachment 142783 [details]
digiKam Trace
In the digiKam trace i do not see a dysfunction. Do you reproduce the crash while this session ? Typically, under Windows digiKam generate a debugger backtrace in your home directory as a text file. To generate this file, you must use the digiKam "debug" version of installer (more heavy installer available in download area). File must be located at C:\Users\_user_name_\AppData\Local\digikam_crash.log Just replace “user_name” with your Windows login account. Best Gilles Caulier This file could be the problem because it is the last one in the log: E:/Photographie/digiKam_Filesystem/2010-2014/2010-Photo/201008-August/20100821-1-Burgschleinitz/20100821-1-Burgschleinitz-0041.tif The main problem is that you are using MySQL 10.6.x. There have been major changes in this MySQL version and the Qt-MySQL driver is no longer compatible without appropriate patches and crashes. The currently compiled digiKam Windows version only works up to MySQL-10.5.x. Maik Created attachment 142795 [details]
Log because digiKam no longer reacts
Hello, digiKam is uninstalled MariaDB 10.6 is uninstalled MariaDB 10.5 installed digiKam ist installed Import into the DB works fine. In my 154,000 photos I find some broken DNG. If I leave them out, they can be imported. DigiKam cannot be started after a pause. No respond. I am enclosing the log. I think I will give up. Thank you for your time, rudolf There are many more messages, something seems to be wrong with your MariaDB installation. I suggest you try digiKam with a SQLite DB first. DBGHELP: C:\Program Files\MariaDB 10.5\bin\ucrtbase.pdb - file not found DBGHELP: C:\Program Files\MariaDB 10.5\bin\dll\ucrtbase.pdb - file not found DBGHELP: C:\Program Files\MariaDB 10.5\bin\symbols\dll\ucrtbase.pdb - file not found Maik Hello, everything is fine. Database on SSD, no longer on Stripset Raid 0 and everything works perfectly. Faulty DNG filtered out, import runs perfectly. Summary: Do not use DNG and no software raid 0. Thanks for the time, rudolf digikam version 7.3.0 Bilder: JPG: 7288 PNG: 4 PSD: 1397 RAW-CR2: 1 RAW-DNG: 108994 RAW-NEF: 1456 RAW-ORF: 2906 RAW-RW2: 386 TIFF: 31657 Gesamt: 154089 : Videos: AVI: 1 Gesamt: 1 : Gesamtzahl der Einträge: 154090 Alben: 3642 Stichwörter: 140 : Datenbanktreiber: QMYSQL Interner Datenbank-Server:: Ja Pfad zum Internen Datenbank-Server: D:/AppData/digiKam/digiKam_Katalog Database locale: System Thank you and have a nice day. |