-
Notifications
You must be signed in to change notification settings - Fork 70
DeadObjectException with SNAPSHOT 3.0.1 #218
Comments
We already get this one with version 3.0.0. Of course without a reproducible use-case |
I am using Mapbox, and I have a SyncAdapter in my app, which runs in a separate process, Mapbox was initialized in Application.onCreate(). So that Mapbox actually was initialized twice: during main app process launch, and everytime when SyncAdapter was running, after ensuring that Mapbox initialized only in main process, this error ALMOST gone. As I remember, the Mapbox in secondary process caused Lost service to be started and not closed, even though the caller process is gone. |
Can confirm it's happening for our app users on multiple phones, Samsung Galaxy A5(2017) (a5y17lte) with Android 6.0, Samsung Galaxy J3(2016) (j3xnlte) Android 5.1, LG Spirit 4G LTE (c70n) Android 6.0 so far. Don't know how to reproduce this behaviour for tests. |
Apart from the above
|
I just notice in my app that my Application onCreate() method is called twice.
|
I guess it is called twice, because Lost service is running in a separate process, so that Application object is created for every process |
Hey, I am trying to upgrade MapBox from
How should I be calling it with |
Hey everyone, we're still working towards actually being able to reproduce this issue so we appreciate your patience in this matter, and appreciate any additional notes towards diagnosing this problem. @lidkxx For your |
@msmollin Thanks! Sorry for asking it up here, had to many github issues opened and thought I'm typing in one of MapBox threads 😬 |
@lidkxx No worries at all. If you could open a separate issue about the |
These are all the crashes im getting in order of the higher number of crashes. One of the crashes might be cause inside mapbox location @tobrun
|
Same stacktrace for StreetComplete users. Looking at the crash reports by Android version, 94% (of 105 reports) of the crashes happen on the same Android version and the same device!:
Hope that information helps to track down the problem. |
I was able to reproduce the steps for one of the crashes above not sure if its caused by mapbox or LOST
`Fatal Exception: java.lang.IllegalStateException: Location update received after client was disconnected. Did you forget to unregister location updates before disconnecting? at com.mapzen.android.lost.internal.FusedLocationServiceCallbackManager.onLocationChanged(SourceFile:31) at com.mapzen.android.lost.internal.FusedLocationProviderApiImpl$1$1.run(SourceFile:47) at android.os.Handler.handleCallback(Handler.java:751) at android.os.Handler.dispatchMessage(Handler.java:95) at android.os.Looper.loop(Looper.java:154) at android.app.ActivityThread.main(ActivityThread.java:6776) at java.lang.reflect.Method.invoke(Method.java) at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:1520) at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1410) ` |
@joaopedro1520 : I made a new bug report for this, lets have one bug report per issue. I created #224 |
@westnordost The deadobject doesn't only happen on that Motorola. In my happy several brands of phones are crashing in all android versions, so it's not that specific |
Also seeing a similar issue on a Nexus 6P and Android 7.1.2. It happens when a route navigation is active and I send the app to the background (press the home button for example).
|
Hey everyone! I just wanted to give a quick update on the status of this issue. Since we've been unable to reproduce this in our sample code in this repository, we took the time to upgrade our complex sample mapping app EraserMap to utilize the latest version of LOST. This resulted in us reproducing one of the issues listed in this issue. You can see the root-cause analysis @sarahlensing performed here: mapzen/eraser-map#824 That said we still have not managed to reproduce the original Thanks for the continued patience here and all the additional support debugging it. Please continue to post any more information you find and in the mean time we're focused on resolving this. |
Since the crash happens on the main thread and users cannot work around it by wrapping LOST related code in try-catch, maybe it would be good to catch a In neither |
Catching this exception will be the way forward. As @msmollin mentioned, we haven't been able to reproduce it but needed to spend time trying to. And as @westnordost says, this shouldn't bring the whole app down. |
i am getting same issue java.lang.RuntimeException: android.os.DeadObjectException at com.mapzen.android.lost.internal.FusedLocationProviderServiceDelegate.reportLocation Mapbox Sdk: com.mapbox.mapboxsdk:mapbox-android-sdk:5.1.0-SNAPSHOT@aar please guide me what can i do for this one Thanks |
I also got crash. SDK: 5.1.0-beta.4 Stack trace:
|
I also got same crash. ANDROID_VERSION=7.0 |
We are encountering a lot of these exceptions, different devices and all Android system versions are affected.
|
Hey Folks, |
I'm re-opening this issue because I would really like if people see this error message to post the log results here. We've continued to have problems actually reproducing this problem and so if you see those log messages (especially @tobrun and friends from Mapbox) put those in here so we can hopefully see if there's anything more we can do. |
Relevant release to the above remarks: https://github.com/mapzen/lost/releases/tag/lost-3.0.2 |
Any news on this? |
@lidkxx As far as we know this has been "fixed" by the above mentioned release. I only re-opened it in the event people are seeing logs to the console with this message. Since there's been no activity since then, I'll probably re-close it for now and if people see the log messages we can reopen as needed. |
There is a repo created by @henrikra that can reproduce this issue every time using older Android devices nitaliano/react-native-mapbox-gl#925 (comment) |
We hit a DeadObjectException using the following SNAPSHOT
Sadly we don't have a reprodicible use-case. Will update the ticket if we have more information.
cc @sarahlensing @Guardiola31337 @zugaldia
The text was updated successfully, but these errors were encountered: