-
Notifications
You must be signed in to change notification settings - Fork 120
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
libc: Fatal signal 11 (SIGSEGV), code 1, fault addr 0x63808001102f10d7 in tid 13696 (FinalizerDaemon) #767
Comments
|
In a fragment you have to call the lifecycle methods in |
Thanks for reaching out @nouman1nv, and thanks for jumping in @arnekaiser! And to confirm - yes, you need to call |
thank you very much @LukasPaczos and @arnekaiser |
A general rule is that you need to follow the view lifecycle inside of the recycler rather than activity/fragment's lifecycle when calling You can also check out the POC in mapbox/mapbox-gl-native#13132. Closing as not-actionable from plugins perspective. |
mapbox through exception Fatal Signal 11
I have a fragment which contain
MapView
. On first time theMapView
loads and every things is perfectly good but when i go to next fragment and then comeback to my oldFragment the code certainly through an exception libc: Fatal Signal 11 i am using version 6.7.0 and using locationComponent apiCan some one please suggest me some things
The text was updated successfully, but these errors were encountered: