https://bugs.kde.org/show_bug.cgi?id=493294
--- Comment #4 from Phrayzur <phr...@gmail.com> --- (In reply to Maik Qualmann from comment #3) > Try to create at least a DebugView log for the crash, or better yet a > backtrace, as described here: > > https://www.digikam.org/contribute/ > > I have already tested the function, it also seems slower to me than it did > some time ago, but I don't have a final answer yet. > Remember that the number of images you are trying to compare is quite large, > each of the 280,000 images must be compared against each other. > > Maik I can do both, but sometimes it doesn't crash. Is there any other info I can provide or record to help? I'm assuming I should restart DigiKam and the duplicate search. If so, would you prefer I start it from maintenance or the similarity tab? I've noticed some huge variations in the speed of duplicate detection. Currently, that's the only thing running to do with the mariadbd.exe process. It's only using 6.3% of the CPU power and only 175 MB of memory but it's accessing the drive at 109.8 MB/s. Wheras Digikam.exe is using 0% CPU, 1834.1 MB of memory and 0 MB/s for the drive. -- You are receiving this mail because: You are watching all bug changes.
