| Summary: | Slow response after tagging | ||
|---|---|---|---|
| Product: | [Applications] digikam | Reporter: | Brian M <bmguarded-dk> |
| Component: | Bundle-Windows | Assignee: | Digikam Developers <digikam-bugs-null> |
| Status: | RESOLVED NOT A BUG | ||
| Severity: | major | CC: | caulier.gilles, metzpinguin |
| Priority: | NOR | ||
| Version First Reported In: | 6.3.0 | ||
| Target Milestone: | --- | ||
| Platform: | Microsoft Windows | ||
| OS: | Microsoft Windows | ||
| Latest Commit: | Version Fixed In: | 7.0.0 | |
| Sentry Crash Report: | |||
| Attachments: |
Windows DebugView output - 2019-11-14_Digikam_6.3.0_BugReport.txt
Windows Resource Monitor - wait chains |
||
Created attachment 123959 [details]
Windows Resource Monitor - wait chains
Tried to close the application and the process continues to run. See wait chains report from Windows Resource monitor
From the debug trace, i can see Exiv2 update file metadata while tag changes. Can you try to reproduce the problem with all metadata options disabled from Setup/Metadata config dialog ? Also, the 6.4.0 release is out. Please try to reproduce with this version. Gilles Caulier You have a broken hard drive many of your images can not be loaded anymore!!! That's why it's slow. Maik Brian, Have you seen last comment from Maik, about your broken hard drive ? Gilles Caulier Ok this file is not relevant of a digiKam problem. Closed... Hi Gilles/Maik, I am really sorry at not replying to your request, as the responses were in my spam filter. Maik - Why do you think it is a broken hard disk? I am successfully using my local drive and NAS HDD. I do not have any problem writing reading files to either of the HDD from other applications. Thanks, Brian Many of your images cannot be loaded because you are using a network path. DigiKam does not support a network path, you have to mount the collection on a drive letter. Furthermore, there was still the problem with the locked database that has now been resolved when scanning. Maik I had overlooked the jpeg error that it reports an empty file due to the network path. As I said, not all file functions in digiKam can process network paths. We already have a bug report for this. Maik Hi Maik, Many thanks for the quick response. I was not aware that only mapped drives can be used. Thanks for and adding clarity on the functionality. I will now change to mapped drives. Thanks, Brian |
Created attachment 123958 [details] Windows DebugView output - 2019-11-14_Digikam_6.3.0_BugReport.txt SUMMARY STEPS TO REPRODUCE 1. Selected Photos - add tag ("Christmas") 2. Very Slow response to add tags. Left overnight to complete activities 3. After returning many hours later to interact with digikam, interactions was very slow. OBSERVED RESULT Very slow response after the tagging was complete EXPECTED RESULT Quicker tagging Smooth user interaction after tagging SOFTWARE/OS VERSIONS Windows: Windows 10 ADDITIONAL INFORMATION Note I ham using windows 10. My images are on a synology NAS (the box) connected over Ethernet The images are accessed using a unc name \\thebox The NAS is connected usin smb3 (I think)