-
-
Notifications
You must be signed in to change notification settings - Fork 335
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
Android x86_64 emulator crashes (11.2.0) #2791
Comments
Happens also to me. And I can confirm it is crippling development. Android API 30, x86_64 emulator. Developing on Linux (Lubuntu 20.04) Platform: Android 11 Version 11.2.0 (tested on StreetComplete streetcomplete/StreetComplete@3d5abf0 )
|
And if I can provide further debugging info I would be happy to spend time on this. Just tell me what should be done. |
The last time simulator problems came up, we concluded those are upstream bugs that should be reported to the Android team at Google. At the same time, MapLibre Android just doesn't work in the simulator, that seriously hinders developing with the library, so we should be aware of this. @mwilsnd @sjg-wdw Should we perhaps define some minimal functionality that we want to work in the simulator, and run some tests on CI to ensure that does not break? |
Can confirm crash, Android API 35 on x86_64 emulator running in Windows 11.
Please advise if we can test anything further to mitigate that problem, just like @matkoniecz said, we'd like to help in any way possible. K |
Would be nice to have a standard way of seeing these stack traces. In general, the simulator is a bit flakey. You might be able to turn functionality off on the simulator, depending on what it is. Let's kick it around at the next meeting. |
The stacktrace is familiar and this might be related to this ticket. |
When the majority of our screens have a map of some sort on them, this causes our entire e2e test suite to be effectively useless, so we can't update to v11.2.0+ Which is a shame because it includes some other stuff we're looking forward to using. This occurs on emulators running different android versions, but haven't tried on a non x86_64 emulator yet. |
More and more users are report being blocked by this. I am considering making a release with the legacy renderer. Its intended use will be purely to have something that works well in the simulator. How do you feel about this? Do we have a clear picture of what is causing the crash? Would be good to report it at Google as well. |
This comment was marked as off-topic.
This comment was marked as off-topic.
Let's keep the discussion focused on the emulator crashes here. |
Just copying some details here from a thread on Slack:
@mwilsnd will make a PR to mitigate the issue by deleting all drawables every frame before running We will have a normal release up with this workaround for the simulator soon. |
This is not reproducible with |
@westnordost but is it also fixed in latest non-Vulkan (OpenGL) release? Or does that one still crash the emulator? |
Crashed for me using the version org.maplibre.gl:android-sdk:11.8.0 using one of the Android API 34 x86_64 emulator
|
Describe the bug
On displaying the map, the Android emulator now crashes. This is new in MapLibre native for Android 11.2.0.
Log:
Bugreport (via
adb bugreport
):bugreport-sdk_phone64_x86_64-UE1A.230829.036.A1-2024-08-31-16-55-40.zip
To Reproduce
Display a map with an Android API 34, x86_64 emulator.
Expected behavior
Doesn't crash.
Video
Screen_recording_20240831_190907.mp4
It doesn't crash immediately but while zooming in somewhere - my guess is: something with rendering glyphs or icons.
Platform information:
Additional context
I know you are not fond of fixing crashes that (possibly) only occur on emulators, but
The text was updated successfully, but these errors were encountered: