Bug 497325

Wich map type are used ? GoogleMaps, OSM, Marble ?

I'm using Marble Virtual Globe with OpenStreetMap. Weird thing is that after last freeze was gone through, digikam started to behave normal way, and automatically zoomed in to location of last use, without any delay/freeze since. There has been many system updates lately so maybe some of them has solved the problem. I will update if problem starts again.

Map was now zoomed out when opened for some unknown reason (instead of starting zoomed in to last location, while selection itself was retained). However digikam had no trouble to place the markers - so no actual trouble this time.

Not fixed. Map has worked well since last occurrence, but was now very slow again. Map is zoomed out on start, and took 5 minutes to get through the freeze - during that time digikam was completely unresponsive using 50% CPU.

Is there anything that can be done to this?

Selecting map tab from left causes digikam freeze for several minutes. During that time ui doesn't react to anything. Eventually process finishes, geolocation pins appear to map and area selections can be normally done, but launching takes too much time.

Bug still exists in 8.6.0. I'm unsure if the zoom out map causes this but it could be part of the problem.

Now on occasional startup when map was expectedly *ZOOMED IN everything worked in reasonable time* , so this zoom out issue is definitely part of the problem which should be fixed. 

Previously map was always zoomed to last location, recently it has started from globe view and possibly counting all itmes takes too long time that way. But as this behavior is now random, there could be something else wrong too.

Hi,

The new AppImage bundle 8.7.0 pre-release for Linux based on Qt 6.8.3 is
online at usual place :

https://files.kde.org/digikam/

Let's me know if the problem remain.

Best regards

Gilles Caulier

I could test 8.7.0 but before I do that, is there a reason to expect it's fixed there as this problem started with earlier version.

Because i rebuild all the bundles from scratch (Windows, Mac, AppImage) with all dependecies up-to-date, and especially Qt frameworks and KDE frameworks.

The bundle are a long process to build (many hours by item), with a complex puzzle to solve to achieve. It's know that some problems have be (mysteriously) solved like this (especially ones that we cannot reproduce...)

Best

Gilles Caulier

Like bug 478503 for ex...

I did download the build now, but problem appeared on first launch trying to open the map. Last time with stable version apparently caused my computer overheat and crash so I chose to terminate the application this time and am reverting back to stable. Last 5+ times or so with stable started the map quite ok but the freezing problem now came back again. 

Coincidentally I'm also having some problems with hibernating my system (similarly takes minutes and freezes the system while doing so) - I think it occurs only when digikam is open but I haven't tested this. This has been going on for some time now, and it *could* be the same time this map issue started again but at this point this is just guessing.

Created attachment 182246 [details]
map freezing 1/2

This log contains all from the point of starting initiating the map after digikam has first finished launching. CPU is all the time around 60%. Scrolled out and moved around map to the point of freezing. No single marker has appeared to map after several minutes waiting. 1/2

Created attachment 182247 [details]
map ready after freezing 2/2

beginning of the log after map loading finishes and works normally. 2/2

Would switching from SQLite to MySQL-Internal help? I also don't have WAL enabled - db is on HDD. I have large database but I haven't noticed any other latency issues.

Hi,

I think no. the database type do not must change anything to display the map.

It sound like a network latency to get the map data from the Internet.

Best

Gilles Caulier

Map should work without internet. I try disabling the internet while opening map for now on. First try opened it like it should to the place where it was last left without being scrolled out to 0 0, but it has worked correctly for short periods before. Will continue testing.

FYI Last time map was zoomed out and pointing to 0 0 but no delay was present as internet connection was disabled. So it seems that loading map via internet for some reason causes the problem. I will continue testing with this workaround.

no luck, digikam frost again while network was disabled.

ok, it can be a GPU issue. Typically the map rendering use QtWebEngine to draw contents which can use OPenGL in the background.

Go to DK/Setup/Miscs/System and enable the OpenGL Software option. Restart digiKam and try again.

Gilles Caulier

I have this enabled now and will continue testing in normal use. First dk-restart was ok, but this could need whole system restart for the problem to be able to reappear.

This setting doesn't fix it. Worked well for over a week but is freezing again. It seemed to be scrolling ok from 0 0 to preferred location, but when I tried to draw rectangle without any items yet appearing on map it stopped. After terminating processes and restarting map is still freezing, so this process has to be waited to finish before being able to access the feature again.

Ok another point to check.

Marble widget used to render the map uses a cache in your home directory:

~/.local/share/digikam/marble_data/maps/earth

Look if directory exists, if your home directory is not full, or if the right to create/use this directory is fine.

Create a backup of the ~/.local/share/digikam/marble_data and remove it. It will be created again at next digiKam session.

We will seen if the problem remain.

Best

Gilles Caulier

Freezing immediately at first try.

All fine directory wise: new files were being created and there's disk space. After deleting new directories were created as expected, but this didn't fix the problem.

Updated to 8.7.0 and repeated deleting marble_data directory. Now it worked correctly so at least that doesn't seem to automatically cause the issue. (Unless the upgrade somehow now fixed this, but possibly not?)

It's frozen again so nothing was accidentally fixed in upgrade.

Lately I had been able to use the map about a week without serious problems after initial freezing, but after I deleted the original directory the map (again) started to freeze on every occasion. I don't know how this is possibly related to the main issue?

Ok, we will process differently.

Install Marble application (digiKam use a dedicated Qt6 port since 2 years now)
Try to reproduce the problem playing with map using the same context (map, zoom level, etc).

Also take a look to the Marble bugzilla, there are similar reports:

https://bugs.kde.org/show_bug.cgi?id=305195
https://bugs.kde.org/show_bug.cgi?id=162681
https://bugs.kde.org/show_bug.cgi?id=339115
https://bugs.kde.org/show_bug.cgi?id=286982
https://bugs.kde.org/show_bug.cgi?id=195515
https://bugs.kde.org/show_bug.cgi?id=311119

all files are closed and older. The last one is important as it highligh a possible problem to render cloud using possible data from the web. In digiKam you can disable the overlay to only show the map substance...

Best

Gilles Caulier

The problem won't be with Marble. I've looked at your log again; you've selected a coordinate range that includes over 180,000 images. Loading that many images into the Item Model and Marble Model simply takes time. There's nothing we can do about it quickly.

In the future, we'll have to switch to a model loading system that only loads the part that currently needs to be displayed in the view

Maik

As I said earlier map often starts with zoomed out to 0 0 coordinates. This has been the most consistent indication that freezing soon occurs when I start closing to preferred location. (Things have been more random lately after trying different settings and for some reason the freeze didn't always occur even when map was zoomed out to nowhere.) 

Expected behavior is and has been that map starts from last location where it was left. This has been consistent behavior for 10+ years. For some reason this has changed i think at the time this problem started. And if the problem is as you say in loading map tiles, the problem will be pretty much fixed if the earlier behavior at start is fixed back as a consistent feature.

Created attachment 183153 [details]
map view opened

This is the map view opened most if not every time freezing occurs. This is nothing I have chosen to be opened. After I tested two different settings (disabling network and OpenGL Software) for some reason this didn't always cause a freeze but I could use the map feature about a week without problems while startup location was random between last left and this zoomed out view.

Is there a fix for this to be expected in next release?

Possibly quickest fix would be to ensure that map starts every time from the location and zoom level it was left last time. Now it mostly prefers to open zoomed out to origo which started when the problems started. This can't be hard to fix?