Created attachment 108289 [details] Unusable Map Dialogie In the following use-cases, it takes approximately 30-35s for the map to appear after the first launch. Thereafter there is no problem: 1. Clicking either Map in the fly-out menus. 2. Selecting a thumbnail then Ctrl_Shft+G. 3. If a map was visible when digiKam was shutdown previously, it then takes 30s for main digiKam window to appear after splash screen disappears on next relaunch. See attached screenshot while waiting for map to load when starting Geo Editor.
this is due certainly of a Marble plugin playing with a remote web service hile the map is displayed. Go to the directory where is installed digiKam. There is a plugins/ sub directory containing a lot of lib*plugin.dll files. There are Marble plugins. Do not look in others sub directories inside plugins/ there are here for others reasons. To find the right dll file introducing this time latency, remove step by step one dll file and restart digiKam to try to reproduce the problem. Gilles Caulier
The problem is not Marble under Windows. Google maps stops after 50% maps loading and then hang a while. If Marble is set as display, the dialog will open quickly. Maik
Maik, The guy who report this file has previously seen a problem with a bad installation of Marble files in Windows bundle. I fixed that and now, the Geolocation map view take a while to be suitable. So i suspect that Marble plugins introduce a dysfunction here, because when no marble plugins are loaded, the problem do not exist. Gilles
No, Marble is ok. I've been watching this delay for some time. But I am of the opinion that it is so extreme only in the virtual machine. I test it tomorrow on a real Windows machine. I use the current Windows-5.8.0 build. Maik
You can also trigger the problem by opening the online manual via the built-in webkit browser. Maik
(In reply to caulier.gilles from comment #1) > this is due certainly of a Marble plugin playing with a remote web service > hile the map is displayed. > > Go to the directory where is installed digiKam. There is a plugins/ sub > directory containing a lot of lib*plugin.dll files. There are Marble > plugins. Do not look in others sub directories inside plugins/ there are > here for others reasons. > > To find the right dll file introducing this time latency, remove step by > step one dll file and restart digiKam to try to reproduce the problem. > > Gilles Caulier Do you guys still want me to check all the DLLs or are you certain it's not Marble plugins?
Checking to remove the dlls will take few minutes to tests. Please confirm or not that problem come from Marble. Thanks in advance Gilles Caulier
I do not think it's any of the plugins in particular. With all the plugins present, the delay is 40s. If remove half the plugins, this delay roughly halves to 20s. If I delete another half of the plugins again, the delay halves again to 10s. It appears to be an overhead per plugin. Do you think that's plausible or am I seeing a pattern that's not there?
yes, it's a side effect of plugins as i expected. As mostly try to be connected to a remote web service, some network time latencies are introduced in your configuration. It's certainly not the only one origin of the problem, as Maik said previously, but removing unwanted plugins will help in this case. This willl also reduce the bundle sizes definitively. Gilles Caulier
I can define the problem more accurately now. If the maps fly-out menu is assumed to be selected: - If I had selected Google Maps in the previous digiKam session, I get the 40s delay at next start-up. By delay I mean in the splash screen, it stops at "Loading KIPI Plugins..." for ~40s. - If I have selected Marble Virtual Globe in the previous digiKam session, I get no delay at next start-up. - If I have selected Marble Virtual Globe in the previous digiKam session, I get no delay at next start-up but if I then select Google Maps in the fly-out menu, I get a ~40s delay to show the Google map. It's definitely connected to Google Maps. I will try it on my Linux machine now....
PS. Synology Photo Station also uses Google Maps and there is no such delay. So I don't think there's general problem accessing Google Maps from my Internet connection.
digikam-5.8.0-01-i386.appimage works fine so it just looks like the Windows version has the problem.
This problem is still present in digiKam-5.8.0-20171113080253-Win64.exe. 5.7 didn't have this issue at all. Is there anything more I can do help you resolve this?
This problem still reproducible with current 5.8.0 - pre-release Windows bundle available here : https://files.kde.org/digikam/ Gilles Caulier
Yes, it' still there.
Created attachment 109411 [details] Debug Log Log attached. It seems the 30s delay takes place after line 194. Incorrect parameter. 00000194 11.94422817 [3024] onecoreuap\shell\lib\bindctx.cpp(128)\explorerframe.dll!00007FFE1270377F: (caller: 00007FFE126DAA6F) ReturnHr(73) tid(2968) 80070057 The parameter is incorrect.
You seem to have fixed this in 5.9. Many thanks!