Android source code(7.1) message-Handler 机制

最新推荐文章于 2021-05-27 13:40:12 发布

chenshuwan

最新推荐文章于 2021-05-27 13:40:12 发布

阅读量405

点赞数

分类专栏： android 文章标签： android 源码 handler详解

本文链接：https://blog.csdn.net/chenshuwan/article/details/69524945

版权

本文深入探讨了Android Handler-Message机制的工作原理。主要内容包括Looper如何维护消息队列，主线程与子线程中Looper的创建方式，以及Message的处理流程。通过分析Looper.java的关键代码，解释了Looper、MessageQueue以及Handler之间的关系，展示了Handler发送和处理Message的过程。同时，提到了HandlerThread在Handler操作中的应用，并指出主线程的Looper在ActivityThread.main方法中初始化。

摘要由CSDN通过智能技术生成

Message handler处理原理：
1、handler-msg 用Looper维护了一个消息队列，采用for死循环对这个队列进行遍历，当有新的msg消息被压入deque时，将会被及时的处理。
2、Main Thread在创建的时候会为当前thread主动分配一个looper，而子线程需要手动创建looper

从code的角度分析一下 message-handler机制是如何运作的

首先，我们来看一下Looper.java里面的主要code

public final class Looper {
   
    static final ThreadLocal<Looper> sThreadLocal = new ThreadLocal<Looper>();
    private static Looper sMainLooper;  // guarded by Looper.class
    final MessageQueue mQueue;
    final Thread mThread;
    private Printer mLogging;
    private long mTraceTag;
    public static void prepare() {
        prepare(true);
    }

    private static void prepare(boolean quitAllowed) {
        if (sThreadLocal.get() != null) {
            throw new RuntimeException("Only one Looper may be created per thread");
        }
        sThreadLocal.set(new Looper(quitAllowed));
    }

    public static void prepareMainLooper() {
        prepare(false);
        synchronized (Looper.class) {
            if (sMainLooper != null) {
                throw new IllegalStateException("The main Looper has already been prepared.");
            }
            sMainLooper = myLooper();
        }
    }

    public static Looper getMainLooper() {
        synchronized (Looper.class) {
            return sMainLooper;
        }
    }

    public static void loop() {
        final Looper me = myLooper();
        if (me == null) {
            throw new RuntimeException("No Looper; Looper.prepare() wasn't called on this thread.");
        }
        final MessageQueue queue = me.mQueue;
        Binder.clearCallingIdentity();
        final long ident = Binder.clearCallingIdentity();

        for (;;) {
            Message msg = queue.next(); // might block
            if (msg == null) {
                return;
            }
            try {
                msg.target.dispatchMessage(msg);
            } finally {
                if (traceTag != 0) {
                    Trace.traceEnd(traceTag);
                }
            }

            final long newIdent = Binder.clearCallingIdentity();
            msg.recycleUnchecked();
        }
    }

    public static @Nullable Looper m