pending synchonization at restart

[Gilles Caulier]

Hi Frederic,

Thanks for reaching out and sharing these details. Lazy synchronization in
digiKam is designed to handle metadata updates efficiently, but
long-running sessions or unexpected interruptions can indeed lead to
questions about its behavior.

* Synchronization After Restart or Crash

When digiKam is closed unexpectedly (e.g., forced restart, power loss, or
crash): pending synchronization tasks are not lost. digiKam tracks metadata
changes in its internal database. Upon restarting digiKam, it will resume
synchronization from where it left off, as it cross-references the database
with the actual file metadata.

If the process was interrupted mid-sync, digiKam will re-attempt the
synchronization for the remaining files during the next session. No data
corruption should occur, but it’s wise to verify a few files manually if
you suspect inconsistencies.

* Blocking Issues During Synchronization

The freezing behavior during synchronization can stem from:

- Large batches of files: Lazy sync processes files in chunks. If a batch
is too large or contains problematic files (e.g., corrupted metadata,
locked files), it may hang.

- File system or network issues: On Windows, permissions, antivirus scans,
or network drives (if applicable) can slow down or block access to files.

- Database locks: digiKam’s SQLite database might occasionally lock if
multiple operations conflict, especially when multi-thread option is
enabled, especially under Windows.

Suggested Steps:

Reduce batch size: In digiKam’s settings (under Metadata → Lazy
Synchronization), try reducing the number of albums to process (e.g., 50 or
100) to avoid overwhelming the system.

Monitor system resources: Ensure your PC has enough RAM/CPU available. Long
sessions can accumulate memory usage especially with multithreading.

Logs: Enable debug logging (in Settings → Configure digiKam → Miscellaneous
→ Logging) and share the logs if the issue persists. This can help pinpoint
the cause. See instructions here :
https://www.digikam.org/contribute/#windows-host

Question: Have you noticed if the blocking issues occur with specific file
types (e.g., RAW, videos) or locations (e.g., external drives)? This might
help narrow it down.
Best regards

Gilles Caulier

Le mar. 25 août 2026 à 19:31, frederic chaume <frederic.chaume at gmail.com> a
écrit :

> aHi all
>
> any ideas ?
> nowadays I'm facing multiple blocking issues ("no respond" , but not
> sure of the message)  when running synchronization , that conduct the
> process to be aborted. Then I'm wondering what is the status of the
> synchronization not completed
>
> thanks and regards
> Frederic
>
>
>
> Le 17/08/2026 à 08:47, frederic chaume a écrit :
> > Hi all
> >
> > Using DK9.1 on win11 and using lazy synchronization for metadata.
> > I noticed that sometimes the synchronization is taking more and more
> > times, generaly when DK is used for long times. Yesterday, I wanted to
> > restart my PC , and it was blocked by the synchronization , and as
> > this never finished , I forced the restart.
> >
> > my question , what about the remaining synchronization ? Is it
> > completed when starting DK again?
> > In fact same question when PC is stopped by a power down or any othe
> > inexpected event
> >
> > regards
> > Frederic
> >
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/digikam-users/attachments/20260825/648fba2a/attachment.htm>