Android Handler源码剖析

作者: phantomvk | 来源:发表于2016-12-12 15:27 被阅读0次

一、Handler用处

Handler有两个主要用法:

  • 计划在将来某个时间点处理Message和Runnable
  • 在不同线程里将一个动作加入Handler所对应的队列去执行

二、成员变量

Handler有4个不可变成员变量:消息队列mQueue、消息队列所属mLooper、可选Handler回调mCallback、可选异步标志mAsynchronous

final MessageQueue mQueue;
final Looper mLooper;
final Callback mCallback;
final boolean mAsynchronous;

三、构造方法

如果线程已经有Looper,那么Handler可以使用下面的构造方法。

public Handler() {
    this(null, false);
}

public Handler(Callback callback) {
    this(callback, false);
}
// 不知道这个异步是不是和指令重排序有关
public Handler(boolean async) {
    this(null, async);
}

public Handler(Callback callback, boolean async) {
    // 判断是否匿名类、本地类、成员类,并判断修饰符是否是static,不是打出就警告信息,避免内存泄漏
    if (FIND_POTENTIAL_LEAKS) {
        final Class<? extends Handler> klass = getClass();
        if ((klass.isAnonymousClass() || klass.isMemberClass() || klass.isLocalClass()) &&
                (klass.getModifiers() & Modifier.STATIC) == 0) {
            Log.w(TAG, "The following Handler class should be static or leaks might occur: " +
                klass.getCanonicalName());
        }
    }
    // 主动获取Handler所在线程的Looper
    mLooper = Looper.myLooper();
    if (mLooper == null) {
        throw new RuntimeException(
            "Can't create handler inside thread that has not called Looper.prepare()");
    }
    mQueue = mLooper.mQueue;
    mCallback = callback;
    mAsynchronous = async;
}

带Looper形参的构造方法,传入的Looper不能为空。通常和Looper.getMainLooper()合用。

public Handler(Looper looper) {
    this(looper, null, false);
}

public Handler(Looper looper, Callback callback) {
    this(looper, callback, false);
}

public Handler(Looper looper, Callback callback, boolean async) {
    mLooper = looper;
    mQueue = looper.mQueue;
    mCallback = callback;
    mAsynchronous = async;
}

四、把Runnable封装成Message

这主要作用是把r赋值给msg.callback,把token赋值给m.obj。因为下一个代码块就使用到这个方法,所以拿到前面先说。

private static Message getPostMessage(Runnable r) {
    Message m = Message.obtain();
    m.callback = r;
    return m;
}

private static Message getPostMessage(Runnable r, Object token) {
    Message m = Message.obtain();
    m.obj = token;
    m.callback = r;
    return m;
}

五、Post和Send

注意下面4个方法:

  • 前两个方法封装形参Runnable,方法名组成是 post()
  • 后两个方法形参是msgmsg.what,方法名组成是 sendMessage()
  • 没有方法形参既有Runnable,又有msg
  • 方法名带Delayed可设置延迟时间,带EmptyMessage为创建空消息
  • 这4个方法的共同点是都调用了sendMessageDelayed(),返回这个调用的结果
public final boolean post(Runnable r) {
   return sendMessageDelayed(getPostMessage(r), 0); //delayMillis = 0 
}
// 时间单位毫秒,如:delayMillis = 1000
public final boolean postDelayed(Runnable r, long delayMillis) {
    return sendMessageDelayed(getPostMessage(r), delayMillis);
}

public final boolean sendMessage(Message msg) {
    return sendMessageDelayed(msg, 0);
}
// msg.what用16进制,如:0x01
public final boolean sendEmptyMessageDelayed(int what, long delayMillis) {
    Message msg = Message.obtain();
    msg.what = what;
    return sendMessageDelayed(msg, delayMillis);
}

SystemClock.uptimeMillis()是从开机到现在的毫秒数,不包括手机睡眠的时间。

postAtTime()重载方法调用了sendMessageAtTime()

public final boolean postAtTime(Runnable r, long uptimeMillis){
    return sendMessageAtTime(getPostMessage(r), uptimeMillis);
}

public final boolean postAtTime(Runnable r, Object token, long uptimeMillis){
    return sendMessageAtTime(getPostMessage(r, token), uptimeMillis);
}

sendEmptyMessage()sendEmptyMessageDelayed()

sendEmptyMessageDelayed()又和sendEmptyMessageAtTime最终调用sendMessageAtTime()

public final boolean sendEmptyMessage(int what) {
    return sendEmptyMessageDelayed(what, 0);
}

public final boolean sendMessageDelayed(Message msg, long delayMillis) {
    if (delayMillis < 0) {
        delayMillis = 0;
    }
    return sendMessageAtTime(msg, SystemClock.uptimeMillis() + delayMillis);
}

public final boolean sendEmptyMessageAtTime(int what, long uptimeMillis) {
    Message msg = Message.obtain();
    msg.what = what;
    return sendMessageAtTime(msg, uptimeMillis);
}

总而言之,上面所有post和send都终结在sendMessageAtTime(),而sendMessageAtTime()仅负责把消息送进消息队列中,然后给一个具体执行时间点。

public boolean sendMessageAtTime(Message msg, long uptimeMillis) {
    MessageQueue queue = mQueue;
    if (queue == null) {
        RuntimeException e = new RuntimeException(
                this + " sendMessageAtTime() called with no mQueue");
        Log.w("Looper", e.getMessage(), e);
        return false;
    }
    return enqueueMessage(queue, msg, uptimeMillis);
}

消息默认是放在消息队列的队尾处。返回成功代表成功进入队列,不代表消息会被调度。

一般情况下,消息队列都会等待所有消息完成才退出。但如果手动关闭消息队列,那滞留在消息队列的消息不会得到处理,然后消息被丢弃,这是进入消息队列却不一定能调度的主要原因。

private boolean enqueueMessage(MessageQueue queue, Message msg, long uptimeMillis) {
    msg.target = this;
    if (mAsynchronous) {
        msg.setAsynchronous(true);
    }
    return queue.enqueueMessage(msg, uptimeMillis);
}

消息也可以放在消息队列的对头优先执行,不过这两个方法只能在非常特殊的情况下采取用,因为顺序问题和未知副作用很容易导致队列后方消息的饥饿。

public final boolean postAtFrontOfQueue(Runnable r){
    return sendMessageAtFrontOfQueue(getPostMessage(r));
}

public final boolean sendMessageAtFrontOfQueue(Message msg) {
    MessageQueue queue = mQueue;
    if (queue == null) {
        RuntimeException e = new RuntimeException(
            this + " sendMessageAtTime() called with no mQueue");
        Log.w("Looper", e.getMessage(), e);
        return false;
    }
    return enqueueMessage(queue, msg, 0);
}

六、调度和三种消息回调

6.1 消息调度

当消息到达预定执行时间,消息所在的Looper就会调用msg.target.dispatchMessage(msg)

public void dispatchMessage(Message msg) {
    if (msg.callback != null) {
        handleCallback(msg);
    } else {
        if (mCallback != null) {
            if (mCallback.handleMessage(msg)) {
                return;
            }
        }
        handleMessage(msg);
    }
}

6.2 三种消息回调方式

(1) 首先dispatchMessage(msg)尝试执行消息体的msg.callback。不过由于上面有EmptyMessage一类方法的存在,所以msg.callback可能为空而不执行。

private static void handleCallback(Message message) {
    message.callback.run();
}

(2) msg.callback不行就看看Handler自己有没有mCallback

public interface Callback {
    public boolean handleMessage(Message msg);
}

例子: 创建Handler时可以实现这个回调,支持操作主线程UI

Handler handler = new Handler(new Handler.Callback() {
    @Override
    public boolean handleMessage(Message msg) {
        return false;
        Toast.makeText(Activity.this,"handleMessage override",Toast.LENGTH_SHORT).show();
    }
});

(3) 如果上两个回调都不存在,就只能寄托于我们自己重写的方法。举个例子:

@Override
public void handleMessage(Message msg) {
    super.handleMessage(msg);
    switch(msg.what){
        case START_ACTIVITY:
            Intent intent = new Intent(Activity.this, MainActivity.class);
            Activity.this.startActivity(intent);
            Activity.this.finish();
            break;
        case TOAST_SHORT_SHOW:
            Toast.makeText(Activity.this, "Toast", Toast.LENGTH_SHORT).show();
            break;
    }
}

七、移除队列消息

根据消息身份what、消息Runnablemsg.obj移除队列中对应的消息。调用那个要根据你选用什么而定。例如发送msg,就用同一个msg.what作为参数。都调用MessageQueue.removeMessages,具体在MessageQueue的源码阅读里面说。

public final void removeCallbacks(Runnable r) {
    mQueue.removeMessages(this, r, null);
}

public final void removeCallbacks(Runnable r, Object token) {
    mQueue.removeMessages(this, r, token);
}

public final void removeMessages(int what) {
    mQueue.removeMessages(this, what, null);
}

public final void removeMessages(int what, Object object) {
    mQueue.removeMessages(this, what, object);
}

public final void removeCallbacksAndMessages(Object token) {
    mQueue.removeCallbacksAndMessages(this, token);
}

八、查找对应消息

上面是移除,这里是查看有没有对应的消息

public final boolean hasMessages(int what) {
    return mQueue.hasMessages(this, what, null);
}

public final boolean hasMessages(int what, Object object) {
    return mQueue.hasMessages(this, what, object);
}

public final boolean hasCallbacks(Runnable r) {
    return mQueue.hasMessages(this, r, null);
}

九、阻塞非安全执行

如果当前执行线程是Handler的线程,Runnable会被立刻执行。否则把它放在消息队列中一直等待执行完毕或者超时。超时后这个任务还是在队列中,在后面的某个时刻它仍然会执行,很有可能造成死锁,所以尽量不要用它。

这个方法使用场景是Android初始化一个WindowManagerService,因为WindowManagerService不成功,其他组件就不允许继续,所以使用阻塞的方式直到完成。

public final boolean runWithScissors(final Runnable r, long timeout) {
    if (r == null) {
        throw new IllegalArgumentException("runnable must not be null");
    }
    if (timeout < 0) {
        throw new IllegalArgumentException("timeout must be non-negative");
    }

    if (Looper.myLooper() == mLooper) {
        r.run();
        return true;
    }
    // 一个阻塞的队列
    BlockingRunnable br = new BlockingRunnable(r);
    return br.postAndWait(this, timeout);
}
IMessenger mMessenger;  // IPC

private static final class BlockingRunnable implements Runnable {
    private final Runnable mTask;
    private boolean mDone;

    public BlockingRunnable(Runnable task) {
        mTask = task;
    }

    @Override
    public void run() {
        try {
            mTask.run();
        } finally {
            synchronized (this) {
                mDone = true;
                notifyAll();
            }
        }
    }

    public boolean postAndWait(Handler handler, long timeout) {
        if (!handler.post(this)) {
            return false;
        }

        synchronized (this) {
            if (timeout > 0) {
                final long expirationTime = SystemClock.uptimeMillis() + timeout;
                while (!mDone) {
                    long delay = expirationTime - SystemClock.uptimeMillis();
                    if (delay <= 0) {
                        return false; // timeout
                    }
                    try {
                        wait(delay);
                    } catch (InterruptedException ex) {
                    }
                }
            } else {
                while (!mDone) {
                    try {
                        wait();
                    } catch (InterruptedException ex) {
                    }
                }
            }
        }
        return true;
    }
}

十、获取消息名

获取消息里Handler的类名,或消息msg.what的16进制值

public String getMessageName(Message message) {
    if (message.callback != null) {
        return message.callback.getClass().getName();
    }
    return "0x" + Integer.toHexString(message.what);
}

获取空消息体的重载方法

public final Message obtainMessage() {
    return Message.obtain(this);
}

public final Message obtainMessage(int what) {
    return Message.obtain(this, what);
}

public final Message obtainMessage(int what, Object obj) {
    return Message.obtain(this, what, obj);
}

public final Message obtainMessage(int what, int arg1, int arg2) {
    return Message.obtain(this, what, arg1, arg2);
}

public final Message obtainMessage(int what, int arg1, int arg2, Object obj) {
    return Message.obtain(this, what, arg1, arg2, obj);
}

十一、其他

剩下这个方法关于跨进程通讯的Messager,在AIDL中使用。

private final class MessengerImpl extends IMessenger.Stub {
    public void send(Message msg) {
        msg.sendingUid = Binder.getCallingUid();
        Handler.this.sendMessage(msg);
    }
}

相关文章

网友评论

    本文标题:Android Handler源码剖析

    本文链接:https://www.haomeiwen.com/subject/jlbmmttx.html