Pattern selector

Most relevant patterns first. Most helpful ones displayed. Click here to show all.

  1. ThreadGroup.uncaughtException() has thrown a DeadObjectException
    Java Runtime
    3
    1
    0
  2. The object you are calling has died
    Android
    76
    244
    2

Your stack trace compared to the selected pattern

Jump to solutionsExpand frames
android.os.DeadObjectException
    at android.os.BinderProxy.transactNative(Native Method)
    at android.os.BinderProxy.transact(Binder.java:496)
    at android.app.ActivityManagerProxy.handleApplicationCrash(ActivityManagerNative.java:4225)
    at com.android.internal.os.RuntimeInit$UncaughtHandler.uncaughtException(RuntimeInit.java:92)
2 frames hidden

Solution

chinthana10 months ago

The object you are calling has died because its hosting process no longer exists. Make sure the invoked class or the activity is still alive and not destroyed in the memory when it is invoked by the caller.

Check the source of this solution for more info

External results for this pattern (10)

  1. frmdstryrvia GitHub1 day ago
    No message found for this stack trace.
    Show stack trace
  2. bemascvia GitHub4 days ago
    No message found for this stack trace.
    Show stack trace
  3. cryptomilkvia GitHub1 week ago
    No message found for this stack trace.
    Show stack trace
  4. SailingLabvia Google Groups1 week ago
    No message found for this stack trace.
    Show stack trace
  5. Sathyavia Google Groups1 week ago
    Transaction failed on small parcel; remote process probably died
    Show stack trace
  6. wofdyvia GitHub2 weeks ago
    Transaction failed on small parcel: remote process probably died
    Show stack trace
  7. ghostvia GitHub3 weeks ago
    No message found for this stack trace.
    Show stack trace
  8. jhackGCvia GitHub3 weeks ago
    No message found for this stack trace.
    Show stack trace
  9. bdndreamsvia GitHub4 weeks ago
    Transaction failed on small parcel; remote process probably died
    Show stack trace