[digiKam-users] DigiKam 7.1.0 - Maxing out Drive and not terminating process on closing

[daihill at tutanota.com]

> Thanks Maik
> Ran Microsoft Debugview spotted a rouge jpg file in my collection, so deleted it and it appears to have fixed the issue. I noticed that anything I tried to do with this file (copy open etc) caused the disk to max out. It also appeared to be the reason DigiKam wasn't terminating properly as it was leaving a background process running. After I deleted the file the backgound process was no longer running and DigiKam closed OK.
> I'll keep an eye one it, but looks like that was the problem. I've attached the log anyway, just in case it helps.
> Thanks
> Dai
>


>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Sun, 11 Oct 2020 08:16:17 +0200
> From: Maik Qualmann <metzpinguin at gmail.com>
> To: digiKam - Home Manage your photographs as a professional with the
>  power of open source <digikam-users at kde.org>
> Subject: Re: [digiKam-users] DigiKam 7.1.0 - Maxing out Drive and not
>  terminating process on closing
> Message-ID: <3266254.Rv0RdV7zmd at linux-tpgn>
> Content-Type: text/plain; charset="us-ascii"
>
> Activate the debug output by setting an environment variable in the Windows 
> environment editor.
>
> Variable:
> QT_LOGGING_RULES
>
> Value:
> digikam.*=true
>
> Download DebugView from Microsoft and run it. Start digiKam and upload the 
> messages from DebugView here.
>
> Maik
>
> Am Sonntag, 11. Oktober 2020, 02:29:12 CEST schrieb daihill at tutanota.com:
>
>> I have been using DigiKam for awhile now and really love it. But today I
>> noticed that after running DigiKam7.1.0 the disk where my collection is
>> maxes out at 100% the moment I launchDigikam. I have turned off "auto scan
>> for new files on startup" Thedrive completely slows down dramatically for
>> any access, read/write or evenjust changing folders. Closing DigiKam didn't
>> change the performance and when Ilooked in system processes DigiKam.exe was
>> still running. The moment I manuallyended the process my disk performance
>> returned to normal.
>>
>>
>> I tried migrating the data baseto my main C drive (ssd) but there was no
>> change - and although the databasewas copied to my SSD it appeared that
>> DigiKam was still using the copy on my"D" drive where it was originally and
>> where my photo collection is.
>>
>>
>> Anyone able to help? as unless Ican find a solution DigiKam for me will be
>> unusable
>>
>>
>> Thanks
>>
>>
>> Dai
>>
>
>
>
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/digikam-users/attachments/20201011/9ad2deee/attachment-0001.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: DigiKam.LOG
Type: application/octet-stream
Size: 69172 bytes
Desc: not available
URL: <http://mail.kde.org/pipermail/digikam-users/attachments/20201011/9ad2deee/attachment-0001.obj>