You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 8, 2023. It is now read-only.
The crash isn't reproducible on demand but always occurs as part of the MapboxMapTest tests.
The trace isn't completely the same every time but it always ends with android::Looper::pollOnce and android::NativeMessageQueue::pollOnce(_JNIEnv*, int).
The text was updated successfully, but these errors were encountered:
While #7451 solves it, I think the underlying issue comes from calling methods on the mapobject from another thread. When you are doing instrumentation testing you are actually running 2 applications, the test application that contains our tests versus the to be tested application. I think the issue comes from running on the main thread of the test application vs the main thread of the to be tested application). @tmpsantos any insights in this crash or on the Android Looper implementation?
@tobrun the crash might not be on the Looper itself. On every thread (including the main thread) all the backtraces will originate from the main loop which is where the thread sleeps. What we need to check here is the topmost frame of the stack.
What you described makes sense a cause of a crash.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
We have seen multiple occurrences of type of crash on CI builds.
The crash isn't reproducible on demand but always occurs as part of the MapboxMapTest tests.
The trace isn't completely the same every time but it always ends with
android::Looper::pollOnce
andandroid::NativeMessageQueue::pollOnce(_JNIEnv*, int)
.The text was updated successfully, but these errors were encountered: