Crashes in production with name EXC_BAD_ACCESS
#1355
Labels
wontfix
This will not be worked on
Comments
|
@naftalibeder, would be cool if you could pepper in some Edit: this applies to the |
|
Sorry for the delay. We did try to do that with a number of our most frequently used instances of |
|
I'm seeing a similar (?) issue with This leads me to the suspicion that there might be a callback fired into the |
That, and even switching to another open sourced flavor of mapbox! Check the installation guide for details |
|
Looks like this was fixed in Maplibre 5.12.0 and Mapbox v6.2.0. Maplibre issue: maplibre/maplibre-native#70 |
|
@arabold @naftalibeder, can you maybe test with the versions @mvanroon recommended? |
|
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Our app has for a long time experienced frequent crashes in production that display the fairly ambiguous name
EXC_BAD_ACCESSor similar.Although the crashing thread almost never references Mapbox, a lot of evidence seems to point to the library being the culprit. Looking at the other threads, there are a lot of references to Mapbox, in particular the
mbgl::resourceURLcalls. This is consistent with what we consider one of the most crash-prone parts of the app, displaying images on the map. At any given time there may be dozens ofSymbolLayerinstances displayed on the map, typically but not always referencing a locally bundled image as thestyle.iconImagevalue, along these lines:Example component setup
My best guess is that this happens on both iOS and Android, but the error logs we get on Android are much less detailed, so it's hard to tell.
Full iOS crash log
Full Android crash log
EDIT: I actually was able to get a stack trace from a crash on the iOS simulator, which I believe is the same issue:
iOS simulator stack trace (crashing thread only)
Obviously, based on this information, it'll be very hard for somebody to provide a useful answer, but I'm trying to work my way towards some possible solutions. I would post in mapbox-gl-native or mapbox-gl-native-ios, but I'm hindered by the fact that I can't reproduce this reliably during testing, and I'm not sure at which level of the stack this is happening.
Does anyone have any ideas of where I could begin?
Current setup (although this problem has been around for a long time, across many different versions):
The text was updated successfully, but these errors were encountered: