wthaem
commented
6 months ago @Phobooky: I can't reproduce neither a hang nor a crash with the given TMS file. Is it in your case a crash or a hang?
If there was a hang, then this could be something I observed earlier without knowing a solution. It happened to me during a very fast sequence of zooming and panning operations. There was an endlessly rotating circle in the map window, no further GUI action was possible. Recommendation in this case: don't have to many GUI actions in a too short time intervall. This behavior most likely depends on the performance of the used PC and its OS.
If there was a crash, then I can't reproduce it.
In the logfile I got plenty of lines of the type you have mentioned. I couldn't find a line in the logfile where a tile load was confirmed. But I loaded successfully hundreds of tiles in the map window. And as a surprise: a cash wasn't built for this TMS.
@kiozen: Do you have an explanation for the last paragraph? Missing "positive" logfile entries and missing cache files I observed for other TMS, too. Again: the tiles were loaded. With timestamp 2023-12-04 I had still cache files saved.
Phobooky
mitxel-m
kiozen
Describe the bug
The last compilation made to resolve an issue has caused an unwanted side effect. The TSM file to get Strava data from the Nakarte Proxy works perfectly for 1.16.1 and 1.17 (QMapShack-1.17.0.1, QMapShack-y 1.17.0.2 builds) but causes QMapShack to crash when zoom-in zoom out with QMapShack -1.17.0.3 when requiring tiles from the Nakarte server. That is, only QMapShack-1.17.0.3 version crashes.
What have you done to circle down the problem?
comment: # Checked with several versions.
To Reproduce
Expected behavior
No hang
Screenshots
Attachments
Tracebacks
In the log you can see numerous requests to the Nakarte proxy website. When the zoom is greater than 16, there are errors, but they do not seem to affect versions prior to 1.17.0.3. But in this case, it seems that coinciding with these errors, the application crashes.
Desktop
Additional context