Bug 504250 - Weird behaviour after long uptime, memory leak?
Summary: Weird behaviour after long uptime, memory leak?
Status: RESOLVED DUPLICATE of bug 502858
Alias: None
Product: digikam
Classification: Applications
Component: Database-Albums (other bugs)
Version First Reported In: 8.6.0
Platform: Microsoft Windows Microsoft Windows
: NOR normal
Target Milestone: ---
Assignee: Digikam Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2025-05-15 07:27 UTC by Andreas Brockhinke
Modified: 2025-05-15 07:34 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Andreas Brockhinke 2025-05-15 07:27:02 UTC 
SUMMARY
Tags no longer displayed after 24h uptime. Possible data loss?

STEPS TO REPRODUCE
Start digiKam. Let it run for a longer time (a day should be sufficient).

OBSERVED RESULT
Album is displayed correctly (thumbs and full size images). However, no tags are displayed.

Initially, I feared that when assigning a "new" tag in that condition all "older" tags would be overwritten.  I checked that for one image and assigned a new tag. That was displayed in digiKam. After committing it, it was correctly written to the file (appended, i.e. it didn't overwrite the "old" tags).
Since I feared data loss, I stopped experimenting. Stopped digiKam and started it again. All tags intact. Behavior back to normal.

SOFTWARE/OS VERSIONS
Behaviour occured on two different machines (both with Windows 11, MariaDB  11.6.2) and fairly large image collections (> 400 k images, 20.000 tags).
Comment 1 Maik Qualmann 2025-05-15 07:34:35 UTC 

*** This bug has been marked as a duplicate of bug 502858 ***