-
Notifications
You must be signed in to change notification settings - Fork 1.3k
SEGV on Android in Style.removeSource() #15182
Comments
Hey @zestyping, thanks for reporting the issue. Are you sure you're not filtering out the proper exception that is printed in the logcat?
when the source is not added to the map beforehand, or:
when the source is Could you place the breakpoint right before the crash again and inspect the call stack for where it originates from on the Maps SDK's side? |
Hmm, I don't see any other messages containing "Mbgl" in the log other than these:
I'll try the breakpoint a bit later today. |
Thanks, @zestyping, let us know about your findings. And btw., those logs were fixed up in #15191. |
This issue has been automatically detected as stale because it has not had recent activity and will be archived. Thank you for your contributions. |
Hello! I just encountered a segmentation violation on Android.
Our Mapbox dependency is declared as:
and our APK is using the armeabi-v7a build of libmapbox-gl.so.
I stepped through the Java code path in the Android Studio debugger, and saw these steps:
My application
—> calls Style.removeSource()
—> calls source.getId()
—> calls nativeGetId()
—> boom! SIGSEGV
I see #11779, which looks in vaguely the same area, though that was an NPE and this is a SEGV so I'm not sure they're related. I assume that a SEGV is always considered a bug in mapbox-gl-native regardless of any improper behaviour by the Java application calling into it, is that right?
Here's the native stack trace:
The text was updated successfully, but these errors were encountered: