Crash during backup process about osmand

[rimaille]

Hi, same problem here, android 11 (rom is RMX3506_11.A.82) on a realme narzo 50i rmx3506.
Osmand from fdroid v4.7.10

Just opening the app and it crash after few seconds.
Deleting cache and rebooting the phone does not work.
Switching from rendering v2 to v1 is OK, Osmand does not crash anymore (thanks Max1234-Ita for the tip)

Here's the logcat.log.
logcat.log

Previous version of Osmand was OK with rendering engine v2, no crash.

[yuriiurshuliak]

The latest crash is in the backup when choosing to download. However, this issue doesn't appear to impact the navigation or post-start crashes, unless there is an issue with the maps. And, If you have live updates enabled, try deleting and disabling them as well.

Please also send us the logcat.log file generated when the app crashes.

[yuriiurshuliak]

Based on the information provided, it appears there are two issues:

• A crash during the backup process when selecting what to download, according to the crash logs in the bug description. exception.log
• A crash related to OpenGL rendering, as noted by rimaille in the comments, "Switching from rendering v2 to v1 is OK, OsmAnd does not crash anymore."

Regarding the second point, it might be related to live updates or another issue. There is no log of this crash.

[yuriiurshuliak]

@Max1234-Ita Could you please clarify if deleting live updates helped resolve the issue? Is this crash still occurring?
If so, please provide a crash video and profile settings.

[Max1234-Ita]

@Max1234-Ita Could you please clarify if deleting live updates helped resolve the issue? Is this crash still occurring? If so, please provide a crash video and profile settings.

Actually the user ended up reinstalling OsmAnd from scratch, anyway he was not using any Live update, just offline vector maps with corresponding 3D relief and contour lines.

The dynamics of his crash, though, were quite similar to the description made by @yuriiurshuliak: some unspecified issue occurred during Cloud sync, then crash and rendering reverted to v1, then the app kept crashing as soon as v2 was re-enabled.

Sorry, but that guy is traveling through the entire Asia and he needed to continue his journey, so that seemed the most viable option.

[kevin-brown]

I'm also running into this issue, but I'm using Android Auto as well and it's causing a total crash of Android Auto which appears to be interfering with the exception logs.

The issue appears to be directly related to the OpenGL/V2 renderer. When I switch to the V1 renderer the crash no longer occurs.

Other fun bits of info for future debugging:

• The crash occurs within minutes of the app being opened in the Android Auto context
• The crash occurs in Free Drive as well as when navigating
• Disabling live updates, removing downloaded live updates, and clearing cache does not solve the problem (which makes me suspect it's unrelated to that issue)
• I've tested and reproduced this among 3 different vehicles with different AA configurations, so I suspect that's not directly related

[yuriiurshuliak]

The initial problem can be fixed by the Android team referring to the exception.log attached above.