-
Notifications
You must be signed in to change notification settings - Fork 272
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
crash during initialising display #1416
Comments
So what is needed next, is finding the commit that breaks your setup. can you git bisect and compile and find the commit that is breaking your setup? |
Sure, I've went through bisect and this is the result:
|
Are you sure about that commit? It only renames icons. |
This is a bugtracker not a forum. |
I'm able to reproduce the problem with XCSoar (latest from Head) on a virtual device, Android 6.0 x86_64. xcsoar.log
logcat
Perhaps this could assist in pinpointing the issue. |
I tried this as well when looking at this problem. |
I fixed the first issue, the ALPHA channel for EGL was missing in the initialization for android. |
The second problem is if the VDPI value is lower than 120, then this logic is not triggered: Lines 49 to 59 in b1244d8
Therefore the Resource name of the bitmap is never appended with the _96 or similar and fails to load the bitmap. Which leads to the above backtrace. |
As I got the device back, I've tested that:
Attached is logcat from commit |
XCSoar versions having the problem
7.42
XCSoar versions not having the problem
7.41
System information
Device: Aquila GPS from PureGliding
Website
Manual
Android info:
Model number: m515
Android version: 6.0
Kernel version: 3.18.22
Build number: MRA58K test-keysV1.920210108
I've cleaned XCSoarData folder.
Steps to reproduce the behavior
Expected behavior
App launches normally.
Actual behavior
Installing 7.41 makes it work fine. Re-installing 7.42 makes it crash again - i.e. this is repeteable.
I'm attaching logcat from the crash, first run after cleaning data folder and re-installation of the XCSoar.
xcsoar.log
The text was updated successfully, but these errors were encountered: