search

mapbox / mapbox-gl-native

Interactive, thoroughly customizable maps in native Android, iOS, macOS, Node.js, and Qt applications, powered by vector tiles and OpenGL
https://mapbox.com/mobile
Other
4.35k stars 1.33k forks source link

Fatal signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x0 in tid 27759 #16543

Open yandroidUA opened 3 years ago

yandroidUA commented 3 years ago

Info:

I've got this error when I'm navigating back to fragment that contains map. I'm using Jetpack Navigation library, so fragments are replacing each other, and version of mapbox SDK is 9.2.0

Problem:

So when I'm opening map firstly all okey, no crash. But when I'm navigating to another fragment and than return back to fragment with map I've got this crash: /libc: Fatal signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x0 in tid 27759

eugeneroz commented 3 years ago

Same issue

ibrahimq21 commented 3 years ago

Same here

rommansabbir commented 3 years ago

Any update on this? The prbolem is same: So when I'm opening map firstly all okey, no crash. But when I'm navigating to another fragment and than return back to fragment with map I've got this crash: /libc: Fatal signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x0 in tid 27759

Android Studio: 4.11 Emulator: Pixel_2_API_29 Mapbox Version: 9.2.0

ziffer1sk commented 3 years ago

Same Problem.

On first load no problem. When I'm changing the map style and re-add the sources E/SensorManager: unregisterListenerImpl sensorName:Rotation Vector Non-wakeup,isWakeUpSensor:false,callingApp: map.dev,callingPid:16444,callingUid:10385 E/SensorManager: registerListenerImpl sensorName:Rotation Vector Non-wakeup,isWakeUpSensor:false,callingApp: map.dev,callingPid:16444,callingUid:10385 A/libc: Fatal signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x0 in tid 16444 (map.dev), pid 16444 (map.dev)

mapbox-sdk 9.5.0

isabsent commented 3 years ago

I catch this bug each time I trying to use Database Inspector in Android Studio under debug. It doesn't depend with mapbox-gl-native usage. When I don't use Database Inspector this bug doesn't appear.