Android Activity Crash (deadobjectexception)
Solution 1:
This exception is caused when you are interacting with a remote process and the remote process was previously killed. I saw it a lot when doing keyboards because the app would try to access our keyboard after it crashed. Here it looks like an activity finished and tried to return to the previous activity, which was already dead. It can probably be safely caught most of the time. But the real solution is to fix the initial crash. You can't have a dead object if the first object doesn't die.
Solution 2:
DeadObjectException extends RemoteException
This Exception means , The object you are calling has died, because its hosting process no longer exists. And check this link for your reference based on DeadObjectException.
Solution 3:
This crash can also happen on AdMob ads (WebViews), when doing frequent orientation changes whilst the ad is loading.
For example, you will see the native C++ crash in webview.apk:
A/libc: Fatalsignal11 (SIGSEGV), code1, faultaddr0x4intid21697A/DEBUG: backtrace:
A/DEBUG: #00pc00d12b44 /system/app/webview/webview.apk (offset 0x7ea000)
followed by the Java crash:
android.os.DeadObjectException
One solution is to install or update the 'Android System WebView' app from the Google Play Store. More info here: https://groups.google.com/d/topic/google-admob-ads-sdk/Q-edauZ27g8/discussion
Post a Comment for "Android Activity Crash (deadobjectexception)"