【问题标题】:NullPointerException in HandlerThreadHandlerThread 中的 NullPointerException
【发布时间】:2016-10-19 20:50:18
【问题描述】:

这个错误让我困惑了好几个小时。我得到 NullPointerException。问题是这个错误不一致。当我启动应用程序时会发生这种情况,但只是偶尔。所以我不确定是什么原因造成的。

对于错误日志中的冗长问题,我深表歉意,但我找不到另一种提问方式。

错误日志如下:

FATAL EXCEPTION: main
Process: com.myproject.android, PID: 22175
java.lang.NullPointerException
    at com.myproject.android.ImageDownloaderThread.queueImage(ImageDownloaderThread.java:74)
    at com.myproject.android.NewsItemPagerActivity$NewsItemFragmentStatePagerAdapter.getItem(NewsItemPagerActivity.java:325)
    at android.support.v13.app.FragmentStatePagerAdapter.instantiateItem(FragmentStatePagerAdapter.java:109)
    at android.support.v4.view.ViewPager.addNewItem(ViewPager.java:832)
    at android.support.v4.view.ViewPager.populate(ViewPager.java:982)
    at android.support.v4.view.ViewPager.populate(ViewPager.java:914)
    at android.support.v4.view.ViewPager.onMeasure(ViewPager.java:1436)
    at android.view.View.measure(View.java:16497)
    at android.view.ViewGroup.measureChildWithMargins(ViewGroup.java:5125)
    at android.widget.FrameLayout.onMeasure(FrameLayout.java:310)
    at android.view.View.measure(View.java:16497)
    at android.view.ViewGroup.measureChildWithMargins(ViewGroup.java:5125)
    at com.android.internal.widget.ActionBarOverlayLayout.onMeasure(ActionBarOverlayLayout.java:327)
    at android.view.View.measure(View.java:16497)
    at android.view.ViewGroup.measureChildWithMargins(ViewGroup.java:5125)
    at android.widget.FrameLayout.onMeasure(FrameLayout.java:310)
    at com.android.internal.policy.impl.PhoneWindow$DecorView.onMeasure(PhoneWindow.java:2291)
    at android.view.View.measure(View.java:16497)
    at android.view.ViewRootImpl.performMeasure(ViewRootImpl.java:1912)
    at android.view.ViewRootImpl.measureHierarchy(ViewRootImpl.java:1109)
    at android.view.ViewRootImpl.performTraversals(ViewRootImpl.java:1291)
    at android.view.ViewRootImpl.doTraversal(ViewRootImpl.java:996)
    at android.view.ViewRootImpl$TraversalRunnable.run(ViewRootImpl.java:5600)
    at android.view.Choreographer$CallbackRecord.run(Choreographer.java:761)
    at android.view.Choreographer.doCallbacks(Choreographer.java:574)
    at android.view.Choreographer.doFrame(Choreographer.java:544)
    at android.view.Choreographer$FrameDisplayEventReceiver.run(Choreographer.java:747)
    at android.os.Handler.handleCallback(Handler.java:733)
    at android.os.Handler.dispatchMessage(Handler.java:95)
    at android.os.Looper.loop(Looper.java:136)
    at android.app.ActivityThread.main(ActivityThread.java:5001)
    at java.lang.reflect.Method.invokeNative(Native Method)
    at java.lang.reflect.Method.invoke(Method.java:515)
    at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:785)
    at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:601)
    at dalvik.system.NativeStart.main(Native Method)

发生这种情况的代码如下所示:

package com.myproject.android;

import java.io.IOException;

import android.graphics.Bitmap;
import android.graphics.BitmapFactory;
import android.os.Handler;
import android.os.HandlerThread;
import android.os.Message;
import android.util.Log;

/*
 * This class is used to download images in the background thread
 */
public class ImageDownloaderThread<Token> extends HandlerThread {

    private static final String TAG = "ImageDownloader";
    private static final int MESSAGE_DOWNLOAD = 0;

    // This is the handler attached to the looper
    Handler mHandler; 






    // The is used as a reference to the main UI thread's handler
    Handler mResponseHandler;

    // This is a listener object that is used to update the main UI thread with the image that is downloaded
    Listener mListener;

    // This is the interface needed when a listener is created. It forces an implementation of the callback in the main UI thread
    public interface Listener {
        void onImageDownloaded(Bitmap image, int pos);
    }

    // Set the listener
    public void setListener(Listener listener) {
        mListener = listener;
    }





    // Constructor
    public ImageDownloaderThread(Handler responseHandler) {
        super(TAG);
        mResponseHandler = responseHandler; // Set the response handler to the one passed from the main thread
    }


    // This method executes some setup before Looper loops for each message
    @Override
    protected void onLooperPrepared() {

        // Create a message handler to handle the message queue
        mHandler = new MessageHandler(ImageDownloaderThread.this);
    }


    // This method is used to add a message to the message queue, so that it can be handled later
    // ... this method is called by the main UI thread to add the message to the queue of the current thread to be handled later
    public void queueImage(String url, int pos) {

        mHandler
            .obtainMessage(MESSAGE_DOWNLOAD, pos, 0, url)
            .sendToTarget();
    }





    // This method is used to download the image  
    private void handleRequest(String url, int pos) {

        try {

            // first check if the url is empty. if it is, then return
            if (url == null) {
                return;
            }

            // Download the image
            byte[] bitmapBytes = new NewsItemsFetcher().getUrlBytes(url);

            // Generate a bitmap
            final Bitmap bitmap = BitmapFactory.decodeByteArray(bitmapBytes, 0, bitmapBytes.length);

            // Set position as 'final'
            final int position = pos;


            // We are using mResponseHandler.post(Runnable) to send a message to the response handler
            // This message will eventually result in the main thread updating the UI with the image
            mResponseHandler.post(new Runnable() {
                @Override
                public void run() {                 
                    mListener.onImageDownloaded(bitmap, position);

                }
            });

        }

        catch (HttpResponseException httpe) {
            // TODO: Handle http response not OK
            Log.e(TAG, "Error in server response", httpe);
        }

        catch (IOException ioe) {
            // TODO: Handle download error
            Log.e(TAG, "Error downloading image", ioe);
        }

    }


    class MessageHandler extends Handler {

        private final ImageDownloaderThread<Token> mImageDownloader;

        MessageHandler(ImageDownloaderThread<Token> imageDownloader) {
            mImageDownloader = imageDownloader;
        }

        // This method is used to process the message that is waiting in the queue 
        @Override
        public void handleMessage(Message msg) {

            // First, check if the message is to download an image
            if (msg.what == MESSAGE_DOWNLOAD) {

                // Call the handleRequest() function which will eventually download the image
                String url = (String)msg.obj;
                int pos = msg.arg1;


                if (mImageDownloader != null) {
                    mImageDownloader.handleRequest(url, pos);
                }

            }
        }

    }

}

如果您想知道,请查看错误日志中的第 74 行(更具体地说,此 at com.myproject.android.ImageDownloaderThread.queueImage(ImageDownloaderThread.java:74) 引用了 queueImage() 中的 .obtainMessage(MESSAGE_DOWNLOAD, pos, 0, url) 代码行


编辑

根据 Loop 的回答中的建议,mHandler 在调用 queueImage() 时为 null。那么,在执行任何queueImage() 调用之前,如何保证mHandleronLooperPrepared() 初始化?

【问题讨论】:

    标签: android message-queue background-thread android-looper android-handlerthread


    【解决方案1】:

    对我来说唯一的原因是 queueImage() 方法在 onLooperPrepared() 之前被调用,所以 mHandler 没有被初始化。

    更新

    HandlerThread 只是一个 Thread,实现了 run() 方法,其中调用了 onLooperPrepared()

    @Override
    public void run() {
        mTid = Process.myTid();
        Looper.prepare();
        synchronized (this) {
            mLooper = Looper.myLooper();
            notifyAll();
        }
        Process.setThreadPriority(mPriority);
        onLooperPrepared();//It's HERE
        Looper.loop();
        mTid = -1;
    }
    

    所以何时调用取决于启动此线程。如果您启动它并立即在该线程的引用上调用公共方法,您可能会遇到竞争条件并且mHandler 未按时初始化。

    一种解决方案是延迟开始处理图像或使用同步技术。但是,我会使用更简单的方法。

    为了清楚起见,您希望在创建 HandlerThread 之后立即初始化您的 mHandler,并且您不想在创建 HandlerThread 的主活动中显式执行此操作。

    更新 2

    只要想出以下解决方案。

    queueImage() 提供简单明了的数据。您可以检查mHandler 是否为空,如果为真,则将queueImage() 的参数添加到该队列。当onLoopPrepared() 被调用时,检查队列中是否有任何东西并处理该数据。

    private LinkedBlockingQueue<Pair<String,Integer>> mQueue = new LinkedBlockingQueue<Pair<String,Integer>>();
    
    public void queueImage(String url, int pos) {
        if (mHandler == null) {
            mQueue.put(new Pair<String,Integer>(url, pos));
            return;
        }
        mHandler
            .obtainMessage(MESSAGE_DOWNLOAD, pos, 0, url)
            .sendToTarget();
    }
    
    @Override
    protected void onLooperPrepared() {
    
        // Create a message handler to handle the message queue
        mHandler = new MessageHandler(ImageDownloaderThread.this);
        //TODO check the queue here, if there is data take it and process
        //you can call queueImage() once again for each queue item
        Pair<String, Integer> pair = null;
        while((pair = mQueue.poll()) != null) {
            queueImage(pair.first, pair.second);
        }
    }
    

    【讨论】:

    • 但是根据 android 文档,onLooperPrepared() 在 Looper 循环之前被调用。确切的措辞是Call back method that can be explicitly overridden if needed to execute some setup before Looper loops.(更多细节,这里是链接developer.android.com/reference/android/os/…)。现在,为什么queueImage() 会在onLooperPrepared() 之前被调用?
    • 顺便说一句,我觉得你的 ID 是 Loop 很酷,我们正在讨论 Loopers :)
    • 您知道,我做了一些测试。你是对的,mHandlernull。我更喜欢您建议的第二个解决方案,但我不愿意跳过一些 queueImage() 电话。如何让queueImage() 等待onLooperPrepared() 完成执行以完成初始化?
    • 你能说明queueImage()被调用的时间和地点吗?
    • 非常感谢。你很有帮助。我很感激你。有效。我会给你十张赞成票,但该网站只允许一张。顺便说一句,我使用了一个 LinkedList 队列,它是由 LinkedBlockingQueue 插入的,因为这个队列只能通过一个线程(后台 Looper 线程)访问。除此之外,一切都很棒。谢谢。
    【解决方案2】:

    我遇到了同样的问题。 我通过在排队消息之前调用 wait() 并在 onLooperPrepared 中调用 notifyAll() 来解决。 这不需要存储待处理消息的其他变量。

    【讨论】:

    • 如果您有能力阻止线程,这是一个很好的答案。我在 Android UI 线程中遇到了这种竞争情况,我无法阻止。
    猜你喜欢
    • 2016-12-19
    • 2018-09-24
    • 1970-01-01
    • 2015-04-07
    • 2014-09-25
    • 2016-03-16
    • 1970-01-01
    • 1970-01-01
    • 2013-07-30
    相关资源
    最近更新 更多