SUMMARY On a clean/fresh boot, for probably 20 beta releases, I have seen this behavior where if I select an album that has some number of images- perhaps 100, perhaps 1000- dont know the trigger if any- a right-click 'find duplicates' command seems to pause for several seconds, and then Digikam crashes (closes with no error message). Strangely, if I restart Digikam without a machine logout or restart (Windows), it doesnt seem to crash for the exact same process. I have no explanation, just the hypothesis that some process remains running post-crash that cases the next instance of that process to behave differently. Memory overrun or who knows- STEPS TO REPRODUCE 1. As outlined, pick a nested folder with some number of files in it- where those images have already been fingerprinted etc 2. Right click on the album, select find duplicates OBSERVED RESULT Seems that on a clean machine/Digikam start, there is a sort of 50/50 chance for a crash. I dont know if this is related to the number of files in the album, or the length of paths etc. But, on restart of Digikam right after crash, a repeat of the same find duplicates command on the same folder doesnt seem to crash- at least I havent seen that happen early in the search process. So, its not something inherent with the folder name or a file count etc EXPECTED RESULT Proper search and output of any matches SOFTWARE/OS VERSIONS Windows: macOS: (available in the Info Center app, or by running `kinfo` in a terminal window) Linux/KDE Plasma: KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION
Hi, We need a debugger backtrace to see where the code crash in the application. Follow the instructions here for Windows: https://www.digikam.org/contribute/#windows-host-1 Gilles Caulier
If you select multiple files in the thumbnail view, the context menu does not include a "find duplicates" option. When selecting a single item, the image similarity search is available. Therefore, if you actually see this option, your menu structure is faulty, or it hasn't been updated. Gilles has made many changes. Delete this file: https://docs.digikam.org/en/getting_started/installation.html Sektion: Contains UI configuration eg. the toolbar contents and positions. If your UI is broken, delete this file Maik
>If you select multiple files in the thumbnail view, the context menu does not include a "find duplicates" option. When selecting a single item, the >image similarity search is available. Therefore, if you actually see this option, your menu structure is faulty, or it hasn't been updated. Gilles has >made many changes. And this is the case in the context menu with current code. From my recent changes, i don't touch the find similar actions. Gilles
The issue was not related to a right click on a thumbnail. It was related to a right click on a tree node, where 'Find Duplicates' exists in the pulldown menu. Im not able to reproduce it as of now. Two things have changed: 1. Yesterday, an initial crash per the bug report, I restarted DigiKam and ran a Find Duplicates from the tree root (the entire tree). That ran- and generated any number of matches (it was set to a tolerance of 60%). I deleted perhaps 100-200 obvious duplicates, but many retrieved were not duplicates (the 60% thing). So I increased the tolerance to 90%, ran again at the root node, and received again a proper list with some errors (fewer non-duplicates). I deleted perhaps 100-200 more. There are several thousand- as a function of merged images from multiple sources- in a source tree of about 130,000 files. 2. Per the instructions in the debug process, I installed the debug version of the snapshot. So, its possible something changed in code. But its also possible there was some specific error with accessing the file system the first try, or perhaps with some particular combination of duplicates that no longer exists due to deletions or file moves. I dont expect this was a function of duplicate count, because the crash happened before any scan began. I think it is possible this was more a function of a file system thing- perhaps a tree with a certain number of files, or perhaps some minimum number of nodes is required (and that is no longer met). What makes no sense to me is- why would this happen on the first try, and then after restarting the application, it would not happen (or at least, typically it did not happen). Presumably, some process was left open in the crash that plays a role here, OR there is some weird thing in the Windows 10 file system- a buffer error or something like that which is set for a volume, and not reset until a reboot happens etc. No idea- just very strange to me that this could persist across app restarts.
Guys- It crashed again this morning, though I didnt have the VS debugger attached at that time. But at least we know the issue remains. I tried a few different processes- reboot, logout/login, deleting files etc, so this may be more random as a function of some other process running. But, I cannot recall any exception to the core pattern- a crash happens on the first instance of selecting 'find duplicates' from an album tree node, and then on restarting digikam, the same scan command process for the same root folder works. So, Ill keep trying. Not exactly clear what Im supposed to do one the crash happens. The overview just talks about saving some particular output, but I havent seen that. Not sure if it is dynamic with a crash event, or nested in a menu etc. lll keep trying- maybe we can find the culprit yet- Best, as always