-
Notifications
You must be signed in to change notification settings - Fork 493
Mapbox crashing after some interval of time #1059
Comments
Sorry I forgot to add in previous crash report. It has following logs also: 05-13 17:12:05.866 24970-25067/<my_application>.debug A/art: art/runtime/indirect_reference_table.cc:116] JNI ERROR (app bug): weak global reference table overflow (max=51200) |
Also, getting continuous message: HomeActivity has HomeMapFragment and HomeMapFragment has com.mapbox.mapboxsdk.maps.SupportMapFragment. |
Here, Sorry for writing many things. I confirm that if app disable location component, app is no more crashing. We very much need the location component in our app, please guide how can we use the location component? Thanking you in advance, |
Thanks for reporting the issue @TankJK. We think that this issue is mainly caused by the AS profiler leak and we don't have a clear resolution yet. FWIW, we've not heard any reports from the production environment. Closing as a duplicate of mapbox/mapbox-gl-native#14010. |
@LukasPaczos I am sorry I didnt get your response. When you say production environment, is it production environment of application or Mapbox? PS: I am always getting this crash when testing so not able to move ahead in my application. Please guide us as we are using Mapbox from last couple of years (with older Mapbox version) and we wanted to upgrade to latest successfully. Thanks. |
I meant that we've never heard any reports from release builds. When it comes to debugging, do you have a minimal reproducible case that we could reliably reproduce with? As others have mentioned in mapbox/mapbox-gl-native#14010, disabling the compass (changing the render mode to |
@LukasPaczos This is always crashing for me and I am using RendereMode#Normal only. I have HomeActivity which has HomeFragment and HomeFragment contains SupportMapFragment. OnMapReady is called on HomeFragment and using this, I am displaying all markers with current location. Getting JNI ERROR (app bug): weak global reference table overflow error after some time (30-150 seconds) and application is crashing. Please guide us we are facing this issue continuously. Thanking you in advance. |
Would you be able to profile the native memory in search for any leaks or unexpected growths? That might help us determine the issue. What's the device you're testing on? |
I am testing on Moto G, Android 7.0. Did you tried using SupportMapFragment? I am sure you can replicate at your end. We are really looking forward to you for resolving this issue. |
@LukasPaczos I tested with non-debug version and its still crashing. Please suggest some solution. |
@LukasPaczos App is getting another continuous crash with InterruptedException. FATAL EXCEPTION: OkHttp events.mapbox.com Writer Device is Android Samsung S5 with Android 5.0 HttpOk library com.squareup.okhttp3:okhttp:3.14.1 is used, is this error due to HttpOk library's latest version? |
@TankJK would you mind cutting a new ticket in the https://github.com/mapbox/mapbox-gl-native/issues explaining the issue and your setup? Thank you! |
@TankJK it does look like internal crash in |
My application is using com.mapbox.mapboxsdk:mapbox-android-navigation-ui:0.37.0 for displaying map and markers (it will also have routes and navigation but still not implemented).
Application is also using com.squareup.okhttp3:okhttp:3.14.1 and
com.squareup.okhttp3:logging-interceptor:3.14.1
Application is displaying the markers using SymbolManager as described in https://github.com/mapbox/mapbox-android-demo/blob/master/MapboxAndroidDemo/src/main/java/com/mapbox/mapboxandroiddemo/examples/plugins/SymbolListenerActivity.java
If application is kept open for certain number of time (30 secs - 150 secs), it crashes automatically without doing anything on it. Please see the attached logs with this issue.
Your help is appreciated.
Thanking you in advance,
TankJK
crash.txt
The text was updated successfully, but these errors were encountered: