Bug 403132

Summary:	Lazy Update not working (or: Stop when I say so)
Product:	[Applications] digikam	Reporter:	Thomas <thomas.albrecht>
Component:	Metadata-Engine	Assignee:	Digikam Developers <digikam-bugs-null>
Status:	RESOLVED FIXED
Severity:	normal	CC:	caulier.gilles, metzpinguin
Priority:	NOR
Version First Reported In:	6.0.0
Target Milestone:	---
Platform:	macOS (DMG)
OS:	macOS
Latest Commit:		Version Fixed/Implemented In:	6.1.0
Sentry Crash Report:

Description Thomas 2019-01-12 10:15:49 UTC

SUMMARY
Recently I added lots of pictures. When I start digikam, it scans for new pictures, as I configured it. But when I quit the program, it still keeps working and won't stop for hours. It seems digikam won't let me interrupt this process (I would have to kill the process).

STEPS TO REPRODUCE
1. Open Digikam
2. Add lots of pictures to an active library (5k)
3. Wait for rescan occur
4. Close digikam (it won't close completely) - e.g. 30-60 mins
5. When the scan is finished, the database operations take their time - e.g. 10 mins
6. finally digikam will close (1 second)

OBSERVED RESULT
Sometimes it freezes, sometimes it closes in the background (I am working on a Mac). When I logged via terminal I found out, that digikam is still scanning (digikam.dimg: "/Volumes/HDD/import/IMG002135g.jpg"  : JPEG file identified).

EXPECTED RESULT
When I quit digikam, I expect it to close - not to lock up. When I restart it, it should continue the scan I've interrupted. I would expect digikam to stop shortly after step 4

SOFTWARE/OS VERSIONS
Windows: 
MacOS: 10.14.2
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version: 

ADDITIONAL INFORMATION
Maybe it would help to split up this process in smaller parts. Write to database after every smaller part?

Comment 1 Maik Qualmann 2019-01-12 15:35:36 UTC

I can not reproduce the behavior here on Linux and Windows. All running tasks are aborted and digiKam terminates immediately. Does it make a difference in OSX, if you over Menu-> Browse-> Close terminate?

Maik

Comment 2 Thomas 2019-01-12 16:07:33 UTC

Well. Right now I am not able to reproduce the behavior again. I will mess around again and post an update again. I was moving folders around while digikam was rescanning. But now everything works as expected. I will try to mess around a little bit more to see if I can reproduce it. In both cases I will post an update.

Comment 3 Thomas 2019-01-13 09:53:02 UTC

I wasn't able to reproduce the descripted behavior in the same manner.

I sorted some folders (albums) within digikam and cleaned up and reorganized several tags. Digikam then started writing xmp files (expected). This took some time so I quit digikam (via menu) so I can continue the next day.
This time I got an popup saying that digikam is still writing xmp files. That was fine. I canceled this dialog and digikam closed as expected.

Next time I will only close the main window. Maybe this will suppress the popup.

Comment 4 caulier.gilles 2019-03-09 04:50:23 UTC

Thomas,

Can you reproduce the dysfunction using 6.1.0 pre-release package for MacOSX available here :

https://files.kde.org/digikam/

Thanks in advance

Gilles Caulier

Comment 5 Thomas 2019-03-23 16:17:03 UTC

No, I wasn't able to reproduce this error anymore. It think it had something todo when I initially scanned all of my images.