HandlerThread
public
class
HandlerThread
extends Thread
java.lang.Object | ||
↳ | java.lang.Thread | |
↳ | android.os.HandlerThread |
A Thread
that has a Looper
. The Looper
can then be used to create Handler
s. Just like with a regular Thread
, Thread.start()
must still be called.
Use this class only if you must work with the Handler
API and need a Thread
to do the handling on that is not an existing Looper
thread, such as Looper.getMainLooper()
. Otherwise, prefer Executor
or ExecutorService
, or Kotlin coroutines.
Note that many APIs that required a Handler
in older SDK versions offer a newer
alternative that accepts an Executor
instead. Always prefer to use
the newer API if available.
Alternatives to HandlerThread
Executor
s offer more flexibility with regards to threading. Work
submitted to an Executor
can be set to run on another thread, on one
of several threads from a static or dynamic pool, or on the caller's thread, depending on your
needs.
{link @link java.util.concurrent.Executor} offers a simpler API that is easier to use compared
to Handler
. {link @link java.util.concurrent.ExecutorService} offers the richer Future
API, which you can use to monitor task status, cancel tasks,
propagate exceptions, and chain multiple pending tasks.
{link @link java.util.concurrent.Executors} is a factory for various Executor
s that meet common concurrency needs. These Executor
s use work queues that offer better concurrency and reduced
contention than HandlerThread
.
On Kotlin, coroutines may be used to handle concurrency.
Common HandlerThread
performance issues
Apps that use HandlerThread
may encounter the following performance issues:
- Excessive thread creation: A
HandlerThread
is aThread
. Every system thread costs some resident memory, whether it is working or if it's idle. If your app has a large number ofHandlerThread
s each dedicated to a single type of task, rather than for instance aThreadPoolExecutor
that can grow and shrink in size according to demand, then the additional idleHandlerThread
s will be wasting memory. - Lock contention:
HandlerThread
uses aLooper
which in turn uses aMessageQueue
.MessageQueue
uses a single lock to synchronize access to its underlying queue. Any threads attempting to enqueue messages at the same time, and theHandlerThread
itself when attempting to dequeue the next message to handle, will block each other. - Priority inversion: A high-priority
HandlerThread
can become blocked by a lower-priority thread, for instance if the former is trying to enqueue a message while the latter is trying to dequeue the next message to handle, or vice versa.
Executor
s or Kotlin
coroutines instead of HandlerThread
.
Summary
Inherited constants |
---|
Public constructors | |
---|---|
HandlerThread(String name)
|
|
HandlerThread(String name, int priority)
Constructs a HandlerThread. |
Public methods | |
---|---|
Looper
|
getLooper()
This method returns the Looper associated with this thread. |
int
|
getThreadId()
Returns the identifier of this thread. |
boolean
|
quit()
Quits the handler thread's looper. |
boolean
|
quitSafely()
Quits the handler thread's looper safely. |
void
|
run()
If this thread was constructed using a separate
|
Protected methods | |
---|---|
void
|
onLooperPrepared()
Call back method that can be explicitly overridden if needed to execute some setup before Looper loops. |
Inherited methods | |
---|---|
Public constructors
HandlerThread
public HandlerThread (String name, int priority)
Constructs a HandlerThread.
Parameters | |
---|---|
priority |
int : The priority to run the thread at. The value supplied must be from
Process and not from java.lang.Thread. |
Public methods
getLooper
public Looper getLooper ()
This method returns the Looper associated with this thread. If this thread not been started or for any reason isAlive() returns false, this method will return null. If this thread has been started, this method will block until the looper has been initialized.
Returns | |
---|---|
Looper |
The looper. |
getThreadId
public int getThreadId ()
Returns the identifier of this thread. See Process.myTid().
Returns | |
---|---|
int |
quit
public boolean quit ()
Quits the handler thread's looper.
Causes the handler thread's looper to terminate without processing any more messages in the message queue.
Any attempt to post messages to the queue after the looper is asked to quit will fail.
For example, the Handler.sendMessage(Message)
method will return false.
If quit()
or quitSafely()
is called multiple times, the first call
will have an effect and the subsequent calls will be no-ops.
Using this method may be unsafe because some messages may not be delivered
before the looper terminates. Consider using quitSafely()
instead to ensure
that all pending work is completed in an orderly manner.
Returns | |
---|---|
boolean |
True if the looper looper has been asked to quit or false if the thread had not yet started running. |
See also:
quitSafely
public boolean quitSafely ()
Quits the handler thread's looper safely.
Causes the handler thread's looper to terminate as soon as all remaining messages in the message queue that are already due to be delivered have been handled. Pending delayed messages with due times in the future will not be delivered.
Any attempt to post messages to the queue after the looper is asked to quit will fail.
For example, the Handler.sendMessage(Message)
method will return false.
If the thread has not been started or has finished (that is if
getLooper()
returns null), then false is returned.
Otherwise the looper is asked to quit and true is returned.
If quit()
or quitSafely()
is called multiple times, the first call
will have an effect and the subsequent calls will be no-ops.
Returns | |
---|---|
boolean |
True if the looper looper has been asked to quit or false if the thread had not yet started running. |
run
public void run ()
If this thread was constructed using a separate
Runnable
run object, then that
Runnable
object's run
method is called;
otherwise, this method does nothing and returns.
Subclasses of Thread
should override this method.
Protected methods
onLooperPrepared
protected void onLooperPrepared ()
Call back method that can be explicitly overridden if needed to execute some setup before Looper loops.