-
Notifications
You must be signed in to change notification settings - Fork 188
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
The application closes itself without crashed. #174
Comments
@EugeneZaychenko, I can't reproduce this issue. |
This is the problem, there is no specific code example. Just running the application with the map is closed or in the NavigationManager.getInstance ().simulate () mode - for some time it also closes. No specific algorithm for action. The only thing that repeats itself is the stack trace. |
Which phone do you use? Maybe the application is closed by some software for power management? As example - MIUI system on the Xiaomi phones has very aggressive power management and it can close application unexpectedly. |
Pixel, HTC M5, Meizu 6 Pro, AVD - all devices have the same error. Since I have no idea what caused this behavior, I rewrite part of the application. When I finish, I will definitely report the result. |
on android devices that have oreo os there is a battery optimization that closes inactive applications. You can programmatically add your app with packagename to ignore battery optimization list.
|
This problem is not only on Oreo and higher and energy consumption is not high. |
@EugeneZaychenko, |
I found a similar problem on stackoverflow.com ( https://stackoverflow.com/questions/17840521/android-fatal-signal-11-sigsegv-at-0x636f7d89-code-1-how-can-it-be-tracked ), but I still haven't figured out what causes it. I have a suggestion that this is somehow related to the Route object. I use Route.serializeAsync and Route.deserializeAsync and the routes created on SDK 3.8 are not reproduced on SDK 3.9 |
@EugeneZaychenko that depends on map version. If map version was updated, then you cannot use serialized route with previous map version. |
I checked and rewired my Java code. Error did not go away, start backtrace: #00 pc 0000000000290b2c /data/app/com.ua.eugenezaychenko.mocklocations-KA-jd6trdJwnrYSsfTjaOQ==/lib/arm64/libMAPSJNI.so (Java_com_nokia_maps_GeoCoordinateImpl_destroyGeoCoordinateNative+104) - this is the path to your SDK. Also consistently shows this error - signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x8 and Cause: null pointer dereference. |
Similar problem mapbox/mapbox-gl-native#10555 |
@EugeneZaychenko,
|
|
I fixed this problem - signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x8. When I removed the field with the GeoCoordinate object from my object. I save the coordinates as Double and then everything works. |
@EugeneZaychenko, |
@EugeneZaychenko, we found and fixed issue with double deletion (it can happen when you call finalize method manually). |
GeoCoordinate was in the data class (entity for the Room library) field. Annotated @ignore. An error occurred when I interacted with the database (write and read). |
Hi! I use Android Premium SDK and the application just closes, without any errors, the only thing that is in the stackTrace I will indicate below. Even if the front service is running, it dies, and after a while it is restored. Since the stackTrace contains references to your inner classes, is there any suggestion that the error is in them? Please check it out?
The text was updated successfully, but these errors were encountered: