Android 消息机制详解

目录

消息机制简介

消息发送

Looper消息循环

IdleHandler

Message复用

异步与同步屏障

消息处理

子线程Looper初始化

参考文献


  • 消息机制简介

Android系统通过Handler、Message、MessageQueue、Looper实现消息机制。Handler负责消息的发送和处理(接收);MessageQueue是消息队列,里面保存了Handler发送的所有的消息(Message),Message是指具体的消息,它持有Handler对象(划重点:这个持有很关键)。Looper执行消息循环,底层是C++的epoll机制,只有在有消息的时候,才会唤醒线程。Looper通过while循环遍历MessageQueque,如果有消息时(MessageQueue中的Message合法),调用Message所持有的Handler对象的dispatchMessage方法分发消息,dispatchMessage最终调用Handler对象的handleMessage方法处理消息。

 消息机制主要用在线程间的通信(通过Message传递数据)。接下来,我们通过一个简单的Demo,从源码的角度来捋一下消息机制。

public class MainActivity extends AppCompatActivity {
    @Override
    protected void onCreate(Bundle savedInstanceState) {
        super.onCreate(savedInstanceState);
        setContentView(R.layout.activity_main);
            final Handler  h = new Handler(){
            @Override
            public void handleMessage(@NonNull Message msg) {
                // 主线程接受消息
                super.handleMessage(msg);
                long id = Thread.currentThread().getId();
            }
        };

        new Thread(new Runnable() {
            @Override
            public void run() {
                // 子线程消息发送       
                long id = Thread.currentThread().getId();
                Message message = new Message();
                message.arg1 = 100;
                message.what = 102;
                h.sendMessage(message);
            }
        }).start();
    }
}

子线程中消息循环需要开启Looper消息循环(  Looper.prepare(); Looper.loop() 这两个方法),否则会异常

public class MyThread extends Thread {
    public static final String TAG = "Zhang";
    public Handler mHandler = null;

    @Override
    public void run() {
        Log.d(TAG, "进入Thread的run");
        // 子线程中需要调用prepare方法初始化
        Looper.prepare();
        mHandler = new Handler(Looper.myLooper()){
            @Override
            public void handleMessage(Message msg){
                Log.d(TAG, "获得了message");
                super.handleMessage(msg);
            }
        };
        // 开启消息循环
        Looper.loop();
    }
}
  • 消息发送

以下4个api都是用来发送消息,but前面三个最终还是调用第四个API,其作用都是向详细队列插入消息。

Handler.post();
Handler.postDelayed();
Handler.postAtTime();
Handler.sendMessageAtTime(); 

frameworks/base/core/java/android/os/Handler.java

/**
  不论是使用postDelayed 或 sendMessageDelayed 或 sendMessageAtTime,最终都是调用enqueueMessage方法,向消息队列插入消息
**/

public final boolean postDelayed(Runnable r, long delayMillis)
{
    return sendMessageDelayed(getPostMessage(r), delayMillis);
}

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

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);
}

//sendMessageAtTime调用enqueueMessage(),将消息插入消息队列。

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

enqueueMessage又调用了MessageQueue的enqueueMessage。

frameworks/base/core/java/android/os/MessageQueue.java

/**
   按照消息处理的先后关系排序,将Message插入链表中的对应位置
**/
 boolean enqueueMessage(Message msg, long when) {
        /**
           检查消息合法性
        **/
        if (msg.target == null) {
            throw new IllegalArgumentException("Message must have a target.");
        }
        if (msg.isInUse()) {
            throw new IllegalStateException(msg + " This message is already in use.");
        }

        synchronized (this) {
            // 正在退出消息循环,不允许继续操作
            if (mQuitting) {
                IllegalStateException e = new IllegalStateException(
                        msg.target + " sending message to a Handler on a dead thread");
                Log.w(TAG, e.getMessage(), e);
                msg.recycle();
                return false;
            }
            
            msg.markInUse();
            msg.when = when;
            // Message链表头
            Message p = mMessages;
            boolean needWake;
           
            if (p == null || when == 0 || when < p.when) {
                // 当前需要处理的消息放在链表的头部
                // New head, wake up the event queue if blocked.
                msg.next = p;
                mMessages = msg;
                needWake = mBlocked;
            } else {
               //将消息按时间顺序插入到MessageQueue。一般地,不需要唤醒事件队列,除非
               //消息队头存在barrier,并且同时Message是队列中最早的异步消息。
                needWake = mBlocked && p.target == null && msg.isAsynchronous();
                Message prev;
                for (;;) {
                    prev = p;
                    p = p.next;
                    if (p == null || when < p.when) {
                        break;
                    }
                    if (needWake && p.isAsynchronous()) {
                        needWake = false;
                    }
                }
                msg.next = p; // invariant: p == prev.next
                prev.next = msg;
            }

            // We can assume mPtr != 0 because mQuitting is false.
            if (needWake) {
                nativeWake(mPtr);
            }
        }
        return true;
    }
  • Looper消息循环

frameworks/base/core/java/android/os/Looper.java

Looper.loop();

public static void loop() {
// 获取当前线程的Looper对象
    final Looper me = myLooper();
    if (me == null) {
        throw new RuntimeException("No Looper; Looper.prepare() wasn't called on this thread.");
    }
    // 获取Looper的消息队列
    final MessageQueue queue = me.mQueue;
    ....
    for (;;) {
        Message msg = queue.next(); // might block
        if (msg == null) {
            return;
        }

        /**
        特别注意:可以通过setMessageLogging(@Nullable Printer printer)方,           
         将自己实现的Printer对象传给mLogging。这样logging就不为空了。分别记录
         L23和L33的时间,来计算消息处理所消耗的时间,从而且判断是否存在ANR。so,
         简单的说,这个可以做性能分析
        */ 
        final Printer logging = me.mLogging;
        if (logging != null) {
            logging.println(">>>>> Dispatching to " + msg.target  +
            msg.callback + ": " + msg.what);
        }
        ...
        try {
            // msg.target就是T1线程的handler.通过dispathcmessage方法将消息发送到消息队列。
            msg.target.dispatchMessage(msg);
          ....

        if (logging != null) {
           logging.println("<<<<< Finished to " + msg.target        
           +msg.callback);
        }
        msg.recycleUnchecked();
    }
}

android.os handler.java

/**
 * Handle system messages here.
 */
public void dispatchMessage(@NonNull Message msg) {
    // 如果消息本身有callback,就调用消息的callback处理
    if (msg.callback != null) {
        handleCallback(msg);
    } else {
    // 如果handler在构造的时候有callback,就调用handler的callback
        if (mCallback != null) {
            if (mCallback.handleMessage(msg)) {
                return;
            }
        }
        // 否则调用重载的handlermessage方法处理消息
        handleMessage(msg);
    }
}


/**

   /**
     * Default constructor associates this handler with the {@link Looper} for the
     * current thread.
     *
     * If this thread does not have a looper, this handler won't be able to receive messages
     * so an exception is thrown.
     */
    public Handler() {
        this(null, false);
    }

**/
  • IdleHandler

IdleHandler是指那些优先级比较低的事务。在处理完所有的Message之后才处理IdleHandler

  • 用法
Looper.myQueue().addIdleHandler(new MessageQueue.IdleHandler() {
    @Override
    public boolean queueIdle() {
        ...
    }
});

MessageQueue.java

public void addIdleHandler(@NonNull IdleHandler handler) {
    if (handler == null) {
        throw new NullPointerException("Can't add a null IdleHandler");
    }
    synchronized (this) {
        // 将IdleHanlder插入mIdlehandler队列中
        mIdleHandlers.add(handler);
    }
}

Looper.myQueue().addIdleHandler方法将IdelHandler对象添加到mIdleHandler队列中。然后在消息循环中,从该队列拿出去,调用IdelHandler的queueIdel方法。具体如下代码:

Message next() {
...
    for (;;) {
        ...

        synchronized (this) {
            ...
            //前面的消息处理完后,再来处理IdelHandler事务
           if (pendingIdleHandlerCount < 0
                    && (mMessages == null || now < mMessages.when)) {
                pendingIdleHandlerCount = mIdleHandlers.size();
            }
            // 如果不存在IdleHandler退出当前循环。
            if (pendingIdleHandlerCount <= 0) {
                // No idle handlers to run.  Loop and wait some more.
                mBlocked = true;
                continue;
            }

            if (mPendingIdleHandlers == null) {
                mPendingIdleHandlers = new IdleHandler[Math.max(pendingIdleHandlerCount, 4)];
            }
            mPendingIdleHandlers = mIdleHandlers.toArray(mPendingIdleHandlers);
        }
        // 轮训,并调用IdleHandler类的queueIdle方法。
        for (int i = 0; i < pendingIdleHandlerCount; i++) {
            final IdleHandler idler = mPendingIdleHandlers[i];
            mPendingIdleHandlers[i] = null; 

            boolean keep = false;
            try {
            // 调用queueIdle方法
                keep = idler.queueIdle();
            } catch (Throwable t) {
                Log.wtf(TAG, "IdleHandler threw exception", t);
            }

            if (!keep) {
                synchronized (this) {
                    mIdleHandlers.remove(idler);
                }
            }
        }
        pendingIdleHandlerCount = 0;
        nextPollTimeoutMillis = 0;

  • Message复用

    synchronized (sPoolSync) {
        if (sPool != null) {
            Message m = sPool;
            sPool = m.next;
            m.next = null;
            m.flags = 0; // clear in-use flag
            sPoolSize--;
            return m;
        }
    }
    return new Message();
}
  • 异步与同步屏障

  • 同步屏障就是阻碍同步,只让异步消息通过。调用postSyncBarrier方法执行同步屏障

    return postSyncBarrier(SystemClock.uptimeMillis());
}

同步屏障就是将一个没有target的msg插入到消息队列中对应的位置。


    synchronized (this) {
        final int token = mNextBarrierToken++;
        final Message msg = Message.obtain();
        msg.markInUse();
        msg.when = when;
        msg.arg1 = token;
         //就是这里!!!初始化Message对象的时候,并没有给target赋值,因此 target==null
        Message prev = null;
        Message p = mMessages;
        if (when != 0) {
            while (p != null && p.when <= when) {
                  //如果开启同步屏障的时间(假设记为T)T不为0,且当前的同步消息里有时间小于T,则prev也不为null
                prev = p;
                p = p.next;
            }
        }
         /根据prev是不是为null,将 msg 按照时间顺序插入到 消息队列(链表)的合适位置
        if (prev != null) { // invariant: p == prev.next
            msg.next = p;
            prev.next = msg;
        } else {
            msg.next = p;
            mMessages = msg;
        }
        return token;
    }
}

再来到消息队列

    ...
        synchronized (this) {
          ...
          // 如果当前msg是同步屏障,就去 找下一个异步消息
            if (msg != null && msg.target == null) {
                do {
                    prevMsg = msg;
                    msg = msg.next;
                } while (msg != null && !msg.isAsynchronous());
            }
            if (msg != null) {
            //  是否到钟? 返回异步消息 - 当前msg就是异步消息
                if (now < msg.when) {
                    nextPollTimeoutMillis = (int) Math.min(msg.when - now, Integer.MAX_VALUE);
                } else {

                    mBlocked = false;
                    if (prevMsg != null) {
                        prevMsg.next = msg.next;
                    } else {
                        mMessages = msg.next;
                    }
                    msg.next = null;
                    if (DEBUG) Log.v(TAG, "Returning message: " + msg);
                    msg.markInUse();
                    return msg;
                }
            } 
            ...
}

移除同步屏障

public void removeSyncBarrier(int token) {
  
    synchronized (this) {
        Message prev = null;
        Message p = mMessages;
        while (p != null && (p.target != null || p.arg1 != token)) {
            prev = p;
            p = p.next;
        }
        if (p == null) {
            throw new IllegalStateException("The specified message queue synchronization "
                    + " barrier token has not been posted or has already been removed.");
        }
        final boolean needWake;
        if (prev != null) {
            prev.next = p.next;
            needWake = false;
        } else {
            mMessages = p.next;
            needWake = mMessages == null || mMessages.target != null;
        }
        p.recycleUnchecked();

        // If the loop is quitting then it is already awake.
        // We can assume mPtr != 0 when mQuitting is false.
        if (needWake && !mQuitting) {
            nativeWake(mPtr);
        }
    }
}

同步屏障总结:

1、MessageQueue.postSyncBarrier方法插入同步屏障到MQ的合适的位置(按照触发时间排序)。

2、MessageQueue.next方法依次取msg。如果当前msg是同步屏障(下图红色),就会找下一个异步消息(msg2)。并将异步消息返回。

3、只要同步屏障存在,且异步消息也存在,同步消息就永无天日。

4、MessageQueue.removeSyncBarrier方法调用后,异步消息失效。异步消息永无天日

 

  • 消息处理

    /**
     * Handle system messages here.
     */
    public void dispatchMessage(Message msg) {
        if (msg.callback != null) {
            handleCallback(msg);
        } else {
            if (mCallback != null) {
                if (mCallback.handleMessage(msg)) {
                    return;
                }
            }
            handleMessage(msg);
        }
    }
  • 子线程Looper初始化

主线程中已经默认初始化,子线程的消息传递需要自己调用Looper.prepare。否则会crash

frameworks/base/core/java/android/os/Looper.java

public static void prepare() {
    // 子线程中,消息循环是可以退出的,quitAllowed为true
    prepare(true);
}
private static void prepare(boolean quitAllowed) {
    if (sThreadLocal.get() != null) {
        throw new RuntimeException("Only one Looper may be created per thread");
    }

    // 将一个Looper对象设置给ThreadLocal
    sThreadLocal.set(new Looper(quitAllowed));
}
private Looper(boolean quitAllowed) {
    // 创建了一个消息队列MessageQueue
    mQueue = new MessageQueue(quitAllowed);
    // 获取当前线程对象
    mThread = Thread.currentThread();
  •  
  • 参考文献

[1]这篇博客将同步屏障讲的非常清楚了,本文引用了该博客的部分图片

https://juejin.cn/post/6844903910113705998

  • 0
    点赞
  • 3
    收藏
    觉得还不错? 一键收藏
  • 1
    评论

“相关推荐”对你有帮助么?

  • 非常没帮助
  • 没帮助
  • 一般
  • 有帮助
  • 非常有帮助
提交
评论 1
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值