Skip to content
GitLab
Explore
Sign in
Register
Primary navigation
Search or go to…
Project
P
platform_frameworks_base-old
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Requirements
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Locked files
Build
Pipelines
Jobs
Pipeline schedules
Test cases
Artifacts
Deploy
Releases
Package Registry
Model registry
Operate
Environments
Terraform modules
Monitor
Incidents
Service Desk
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Code review analytics
Issue analytics
Insights
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
Farzin Kazemzadeh
platform_frameworks_base-old
Commits
0a6c6ad5
Commit
0a6c6ad5
authored
1 year ago
by
Steven Moreland
Committed by
Gerrit Code Review
1 year ago
Browse files
Options
Downloads
Plain Diff
Merge "DeadObjectException: detail what error means" into main
parents
99f6f1ae
aeae313d
No related branches found
Branches containing commit
No related tags found
No related merge requests found
Changes
2
Hide whitespace changes
Inline
Side-by-side
Showing
2 changed files
core/java/android/os/DeadObjectException.java
+23
-2
23 additions, 2 deletions
core/java/android/os/DeadObjectException.java
core/java/android/os/DeadSystemRuntimeException.java
+3
-1
3 additions, 1 deletion
core/java/android/os/DeadSystemRuntimeException.java
with
26 additions
and
3 deletions
core/java/android/os/DeadObjectException.java
+
23
−
2
View file @
0a6c6ad5
...
...
@@ -19,8 +19,29 @@ import android.os.RemoteException;
/**
* The object you are calling has died, because its hosting process
* no longer exists. This is also thrown for low-level binder
* errors.
* no longer exists, or there has been a low-level binder error.
*
* If you get this exception from a system service, the error is
* usually nonrecoverable as the framework will restart. If you
* receive this error from an app, at a minimum, you should
* recover by resetting the connection. For instance, you should
* drop the binder, clean up associated state, and reset your
* connection to the service which through this error. In order
* to simplify your error recovery paths, you may also want to
* "simply" restart your process. However, this may not be an
* option if the service you are talking to is unreliable or
* crashes frequently.
*
* If this isn't from a service death and is instead from a
* low-level binder error, it will be from:
* - a oneway call queue filling up (too many oneway calls)
* - from the binder buffer being filled up, so that the transaction
* is rejected.
*
* In these cases, more information about the error will be
* logged. However, there isn't a good way to differentiate
* this information at runtime. So, you should handle the
* error, as if the service died.
*/
public
class
DeadObjectException
extends
RemoteException
{
public
DeadObjectException
()
{
...
...
This diff is collapsed.
Click to expand it.
core/java/android/os/DeadSystemRuntimeException.java
+
3
−
1
View file @
0a6c6ad5
...
...
@@ -19,10 +19,12 @@ package android.os;
/**
* Exception thrown when a call into system_server resulted in a
* DeadObjectException, meaning that the system_server has died or
* experienced a low-level binder error. There's
*
nothing apps can
* experienced a low-level binder error. There's nothing apps can
* do at this point - the system will automatically restart - so
* there's no point in catching this.
*
* See {@link android.os.DeadObjectException}.
*
* @hide
*/
public
class
DeadSystemRuntimeException
extends
RuntimeException
{
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment