Hi.it support handleMessage or not like this?

    Handler handlerButtonToggleAction = new Handler() {
        public void handleMessage(Message msg) {
            switch (msg.what) {
                case 1:
                    MediaArticle article = (MediaArticle) msg.obj;
                    if (article.isCached()) {
                        showArticleActionDialog(article);
                    } else {
                        toggleArticleCacheStatus(article);
                    }
                    break;
            }
        }
    };

In my project. i have a main handler in activity to update ui by message tag. Thanks.

Some code in activity like this:

new WeakHandler().postDelayed(new Runnable() {
            @Override
            public void run() {
                // do something
            }
        }, 10_000);
``
If the activity finished within 10 seconds, the runnable will not run.Is there any idea to run the runnable after activity destroyed?
P.S.
I found some reason in WeakHandler.java

final ChainedRef mRunnables = new ChainedRef(mLock, null);
//`mRunnables` recycled after activity destroyed so nothing keep reference to the following runnable

WeakHandler should not be used without hard reference from outside. this is from https://techblog.badoo.com/blog/2014/08/28/android-handler-memory-leaks/ Why is that? This is what is meant? Please give an example to explain this.

Just as #11 say: callback sometimes occurs null pointer

I have an idea: Check if tag of callback and tag of message-bundle are same by setting a tag when send message.

It can guarantee a one-to-one correspondence between callbacks and messages.

leak could still occur when used like bellow: WeakHandler handler = new WeakHandler(); Message m = Message.obtain(handler.getExecHandler(), new Runnable() { @Override public void run() { //do something } }); handler.sendMessageDelayed(m, delaytimes);

although postDelay() should be used here, but what if when we get message like this: Message message = Message.obtain(m); and m has a callback?

so maybe sendMessageXX() methods should be optimized:

public final boolean sendMessage(Message msg) {
    if (msg.getCallback() != null) {
        return mExec.post(msg.getCallback());
    }
    return mExec.sendMessage(msg);
}

public final boolean sendMessageAtFrontOfQueue(Message msg) {
    if (msg.getCallback() != null) {
        return postAtFrontOfQueue(msg.getCallback());
    }
    return mExec.sendMessageAtFrontOfQueue(msg);
}

public boolean sendMessageAtTime(Message msg, long uptimeMillis) {
    if (msg.getCallback() != null) {
        return postDelayed(msg.getCallback(), uptimeMillis);
    }
    return mExec.sendMessageAtTime(msg, uptimeMillis);
}

public final boolean sendMessageDelayed(Message msg, long delayMillis) {
    if (msg.getCallback() != null) {
        return postDelayed(msg.getCallback(), delayMillis);
    }
    return mExec.sendMessageDelayed(msg, delayMillis);
}