Low-level class holding the list of messages to be dispatched by a
Looper. Messages are not added directly to a MessageQueue,
but rather through
Handler objects associated with the Looper.
You can retrieve the MessageQueue for the current thread with
|MessageQueue.IdleHandler||Callback interface for discovering when a thread is going to block waiting for more messages.|
Add a new
Invoked when the garbage collector has detected that this instance is no longer reachable.
Add a new
MessageQueue.IdleHandler to this message queue. This may be
removed automatically for you by returning false from
IdleHandler.queueIdle() when it is
invoked, or explicitly removing it with
This method is safe to call from any thread.
|handler||The IdleHandler to be added.|
MessageQueue.IdleHandler from the queue that was previously added
addIdleHandler(MessageQueue.IdleHandler). If the given object is not currently
in the idle list, nothing is done.
|handler||The IdleHandler to be removed.|
Invoked when the garbage collector has detected that this instance is no longer reachable. The default implementation does nothing, but this method can be overridden to free resources.
Note that objects that override
finalize are significantly more expensive than
objects that don't. Finalizers may be run a long time after the object is no longer
reachable, depending on memory pressure, so it's a bad idea to rely on them for cleanup.
Note also that finalizers are run on a single VM-wide finalizer thread,
so doing blocking work in a finalizer is a bad idea. A finalizer is usually only necessary
for a class that has a native peer and needs to call a native method to destroy that peer.
Even then, it's better to provide an explicit
close method (and implement
Closeable), and insist that callers manually dispose of instances. This
works well for something like files, but less well for something like a
where typical calling code would have to deal with lots of temporaries. Unfortunately,
code that creates lots of temporaries is the worst kind of code from the point of view of
the single finalizer thread.
If you must use finalizers, consider at least providing your own
ReferenceQueue and having your own thread process that queue.
Unlike constructors, finalizers are not automatically chained. You are responsible for
Uncaught exceptions thrown by finalizers are ignored and do not terminate the finalizer thread. See Effective Java Item 7, "Avoid finalizers" for more.