crash when opening track details with both Y axis used or track charts

Georg D shared this problem 2 months ago
In Progress

Locus v4.35.0 works fine but crashes when opening
a) the details of certain tracks (i.e. the upper screen half showing map, the lower name, timestamp. statistics, chart, description,...) and in the chart, having left Y axis altitude and right Y axis slope. Not really important for me because I use the detailed chart.
b) the charts window (from the track details window) for certain tracks. Of medium importance to me because I like the possibility to use charts directly in Locus, but can export GPX and do charts in other programs, so a workaround exist.

I have the impression the more track points the more likely a crash.

1 does not happen if right Y axis is disabled. It happens when images are enabled as well as disabled (setting "show media").


2 does happen if "Display all charts" is enabled or disabled, and "shlope colors" enabled or disabled.

1+2 do not happen for all tracks. It happens after rebooting the device. It happens with offline vector maps (OAM) as well as online raster map (OSM Classic). It sometimes restarts Locus automatically, sometimes I need to manually start it again. In contrast to https://help.locusmap.eu/topic/crash-when-moving-to-a-track-that-is-not-in-current-map it also happens when track is completely visible in current map view. For the crashing example track (Boefs) I don't recognize anything special; it is long but nothing exceptional (around 5h45min with custom recording profile "for OSM mapping" 5m 1s), it has only 2 waypoints, it's completely in one map.

Replies (3)

photo
1

Hi Georg,

could you please test it with the latest beta? Thanks

This comment is in trash! Restore
photo
1

Hi Michal, in v4.35.0.8 beta with default settings and without login, the 2nd issue still happens, the 1st not – probably because the free version's chart is too much simplified to cause the issue.

This comment is in trash! Restore
photo
photo
1

Hi Georg,

could you please make a crash report with the built-in crash reporter after the app crashes? Thanks

This comment is in trash! Restore
photo
1

I tried but failed; after step 5, I don't get a confirmation but "Hochladen fehlgeschlagen. This operation is restricted to administrators only". How shall I proceed?

This comment is in trash! Restore
photo
1

Could you please send a screenshot of the message? I'll forward it to the devs. This is quite unexpected behavior.

This comment is in trash! Restore
photo
1

Here you are
1ef9e40cb87a02ffb0e65785be447d58b9232e626d08643cd92b8b6daa862f3c

I tapped "Zum Support hochladen", in next screen "Senden"

This comment is in trash! Restore
photo
photo
1

Hi Georg,

just to be sure - are you logged in to your Locus account when you try to send the bugreport?

This comment is in trash! Restore
photo
1

Hi Michal,

no, it was on my spare mobile where I test the current beta v4.35.8 without my account & settings to rule out these are causing the issues while default setup works fine. Now I tried on my main mobile with Google Play Locus version (v4.35.0) and logged in, uploading worked – I'm surprised I have admin rights in Locus' servers 😁

Upload ID is 41130bd5-f7b

In manual, screenshot of step 3 is outdated, wording changed considerably.

Best regards, Georg

This comment is in trash! Restore
photo
1

The current wording is mentioned in the manual:

8cf62b7410f8948e5ac3dd9b583a50e08c84cb76725ecf79434314644b1c04a4

This part of the app is awaiting a change and the future wording will be "Report bug" again, that's why the screenshot seems "outdated".

This comment is in trash! Restore
photo
Leave a Comment
 
Attach a file
You can't vote. Please authorize!