1. 在MessagelistActivity中出现has leaked IntentReceiver的异常。异常日志如下。

07-15 08:09:53.211: E/ActivityThread(15491): Activity com.txrj.sms.activity.MessageListActivity has leaked IntentReceiver com.txrj.sms.activity.MessageListActivity$6@41e189d0 that was originally registered here. Are you missing a call to unregisterReceiver()?
07-15 08:09:53.211: E/ActivityThread(15491): android.app.IntentReceiverLeaked: Activity com.txrj.sms.activity.MessageListActivity has leaked IntentReceiver com.txrj.sms.activity.MessageListActivity$6@41e189d0 that was originally registered here. Are you missing a call to unregisterReceiver()?
07-15 08:09:53.211: E/ActivityThread(15491):     at android.app.LoadedApk$ReceiverDispatcher.<init>(LoadedApk.java:763)
07-15 08:09:53.211: E/ActivityThread(15491):     at android.app.LoadedApk.getReceiverDispatcher(LoadedApk.java:567)
07-15 08:09:53.211: E/ActivityThread(15491):     at android.app.ContextImpl.registerReceiverInternal(ContextImpl.java:1167)
07-15 08:09:53.211: E/ActivityThread(15491):     at android.app.ContextImpl.registerReceiver(ContextImpl.java:1154)
07-15 08:09:53.211: E/ActivityThread(15491):     at android.app.ContextImpl.registerReceiver(ContextImpl.java:1148)
07-15 08:09:53.211: E/ActivityThread(15491):     at android.content.ContextWrapper.registerReceiver(ContextWrapper.java:348)
07-15 08:09:53.211: E/ActivityThread(15491):     at com.txrj.sms.activity.MessageListActivity.getDeliveryIntent(MessageListActivity.java:247)
07-15 08:09:53.211: E/ActivityThread(15491):     at com.txrj.sms.activity.MessageListActivity.sendMessage(MessageListActivity.java:196)
07-15 08:09:53.211: E/ActivityThread(15491):     at com.txrj.sms.activity.MessageListActivity.access$14(MessageListActivity.java:190)
07-15 08:09:53.211: E/ActivityThread(15491):     at com.txrj.sms.activity.MessageListActivity$2.onClick(MessageListActivity.java:120)
07-15 08:09:53.211: E/ActivityThread(15491):     at android.view.View.performClick(View.java:3567)
07-15 08:09:53.211: E/ActivityThread(15491):     at android.view.View$PerformClick.run(View.java:14224)
07-15 08:09:53.211: E/ActivityThread(15491):     at android.os.Handler.handleCallback(Handler.java:605)
07-15 08:09:53.211: E/ActivityThread(15491):     at android.os.Handler.dispatchMessage(Handler.java:92)
07-15 08:09:53.211: E/ActivityThread(15491):     at android.os.Looper.loop(Looper.java:137)
07-15 08:09:53.211: E/ActivityThread(15491):     at android.app.ActivityThread.main(ActivityThread.java:4517)
07-15 08:09:53.211: E/ActivityThread(15491):     at java.lang.reflect.Method.invokeNative(Native Method)
07-15 08:09:53.211: E/ActivityThread(15491):     at java.lang.reflect.Method.invoke(Method.java:511)
07-15 08:09:53.211: E/ActivityThread(15491):     at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:993)
07-15 08:09:53.211: E/ActivityThread(15491):     at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:760)
07-15 08:09:53.211: E/ActivityThread(15491):     at dalvik.system.NativeStart.main(Native Method)
07-15 08:09:53.221: E/ActivityThread(15491): Activity com.txrj.sms.activity.MessageListActivity has leaked IntentReceiver com.txrj.sms.activity.MessageListActivity$5@41df9b80 that was originally registered here. Are you missing a call to unregisterReceiver()?
07-15 08:09:53.221: E/ActivityThread(15491): android.app.IntentReceiverLeaked: Activity com.txrj.sms.activity.MessageListActivity has leaked IntentReceiver com.txrj.sms.activity.MessageListActivity$5@41df9b80 that was originally registered here. Are you missing a call to unregisterReceiver()?
07-15 08:09:53.221: E/ActivityThread(15491):     at android.app.LoadedApk$ReceiverDispatcher.<init>(LoadedApk.java:763)
07-15 08:09:53.221: E/ActivityThread(15491):     at android.app.LoadedApk.getReceiverDispatcher(LoadedApk.java:567)
07-15 08:09:53.221: E/ActivityThread(15491):     at android.app.ContextImpl.registerReceiverInternal(ContextImpl.java:1167)
07-15 08:09:53.221: E/ActivityThread(15491):     at android.app.ContextImpl.registerReceiver(ContextImpl.java:1154)
07-15 08:09:53.221: E/ActivityThread(15491):     at android.app.ContextImpl.registerReceiver(ContextImpl.java:1148)
07-15 08:09:53.221: E/ActivityThread(15491):     at android.content.ContextWrapper.registerReceiver(ContextWrapper.java:348)
07-15 08:09:53.221: E/ActivityThread(15491):     at com.txrj.sms.activity.MessageListActivity.getSentIntent(MessageListActivity.java:232)
07-15 08:09:53.221: E/ActivityThread(15491):     at com.txrj.sms.activity.MessageListActivity.sendMessage(MessageListActivity.java:195)
07-15 08:09:53.221: E/ActivityThread(15491):     at com.txrj.sms.activity.MessageListActivity.access$14(MessageListActivity.java:190)
07-15 08:09:53.221: E/ActivityThread(15491):     at com.txrj.sms.activity.MessageListActivity$2.onClick(MessageListActivity.java:120)
07-15 08:09:53.221: E/ActivityThread(15491):     at android.view.View.performClick(View.java:3567)
07-15 08:09:53.221: E/ActivityThread(15491):     at android.view.View$PerformClick.run(View.java:14224)
07-15 08:09:53.221: E/ActivityThread(15491):     at android.os.Handler.handleCallback(Handler.java:605)
07-15 08:09:53.221: E/ActivityThread(15491):     at android.os.Handler.dispatchMessage(Handler.java:92)
07-15 08:09:53.221: E/ActivityThread(15491):     at android.os.Looper.loop(Looper.java:137)
07-15 08:09:53.221: E/ActivityThread(15491):     at android.app.ActivityThread.main(ActivityThread.java:4517)
07-15 08:09:53.221: E/ActivityThread(15491):     at java.lang.reflect.Method.invokeNative(Native Method)
07-15 08:09:53.221: E/ActivityThread(15491):     at java.lang.reflect.Method.invoke(Method.java:511)
07-15 08:09:53.221: E/ActivityThread(15491):     at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:993)
07-15 08:09:53.221: E/ActivityThread(15491):     at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:760)
07-15 08:09:53.221: E/ActivityThread(15491):     at dalvik.system.NativeStart.main(Native Method)

2. 出现异常原因分析。在发送信息时,创建了两个PendingIntent,它们是调用方法getBroadcast来发送广播。在此之前调用registerBroadcast注册广播,查看代码找不到注销广播的语句,所以导致出现leaked IntentReceiver的异常。以下是改正之后的代码。

private PendingIntent getSentIntent(final Uri uri) {
    BroadcastReceiver receiver = new BroadcastReceiver(){

        @Override
        public void onReceive(Context context, Intent intent) {
            mContext.unregisterReceiver(this);
            int resultCode = getResultCode();
            if(resultCode == RESULT_OK) {
                Toast.makeText(context, "send message success.", Toast.LENGTH_SHORT).show();
                //Log.i("txrjsms", "send message success.");
                updateMsgType(uri, Sms.MESSAGE_TYPE_SENT);
            } else if(resultCode == SmsManager.RESULT_ERROR_GENERIC_FAILURE) {
                Toast.makeText(context, "Generic failure.", Toast.LENGTH_SHORT).show();
                updateMsgType(uri, Sms.MESSAGE_TYPE_FAILED);
            } else if(resultCode == SmsManager.RESULT_ERROR_NO_SERVICE) {
                Toast.makeText(context, "service is currently unavailable.", Toast.LENGTH_SHORT).show();
                updateMsgType(uri, Sms.MESSAGE_TYPE_FAILED);
            } else if(resultCode == SmsManager.RESULT_ERROR_NULL_PDU) {
                Toast.makeText(context, "no pdu provided.", Toast.LENGTH_SHORT).show();
                updateMsgType(uri, Sms.MESSAGE_TYPE_FAILED);
            } else if(resultCode == SmsManager.RESULT_ERROR_RADIO_OFF) {
                Toast.makeText(context, "radio was explicitly turned off.", Toast.LENGTH_SHORT).show();
                updateMsgType(uri, Sms.MESSAGE_TYPE_FAILED);
            }
        }
    };
    IntentFilter filter = new IntentFilter(TxrjConstant.ACTION_SEND_SMS);
    mContext.registerReceiver(receiver, filter);
    Intent sentIntent = new Intent(TxrjConstant.ACTION_SEND_SMS);
    return PendingIntent.getBroadcast(mContext, 0, sentIntent, 0);
}

 

private PendingIntent getDeliveryIntent() {
    BroadcastReceiver receiver = new BroadcastReceiver(){

        @Override
        public void onReceive(Context context, Intent intent) {
            mContext.unregisterReceiver(this);
            Toast.makeText(context, "message arrived.", Toast.LENGTH_SHORT).show();
            //Log.i("txrjsms", "message arrived.");
        }
    };
    IntentFilter filter = new IntentFilter(TxrjConstant.ACTION_DELIVERY_SMS);
    mContext.registerReceiver(receiver, filter);
    Intent deliveryIntent = new Intent(TxrjConstant.ACTION_DELIVERY_SMS);
    return PendingIntent.getBroadcast(mContext, 0, deliveryIntent, 0);
}

3. 添加了注销广播接收器的语句之后还会有问题。比如,发出信息之后,对方有信息回复时,在MessageListActivity界面中无法将刚收到的信息显示出来。优化注册和注销Receiver的代码。以下是优化过的代码,将receiver作为实例变量来定义,在第一次获取sentIntert和deliveryIntent时创建并注册它们。在onDestroy方法中注销它们。

在sentReceiver中需要传递表示发送信息的uri。在调用getBroadcast时通过intent.putExtra放入Uri。在onReceive方法中通过intent.getParcelableExtra取出Uri。

private void createAndRegisterSentReceiver() {
    sentReceiver = new BroadcastReceiver(){
        @Override
        public void onReceive(Context context, Intent intent) {
            Uri uri = intent.getParcelableExtra(TxrjConstant.EXTRA_SENT_URI);
            int resultCode = getResultCode();
            if(resultCode == RESULT_OK) {
                Toast.makeText(context, "send message success.", Toast.LENGTH_SHORT).show();
                updateMsgType(uri, Sms.MESSAGE_TYPE_SENT);
            } else if(resultCode == SmsManager.RESULT_ERROR_GENERIC_FAILURE) {
                Toast.makeText(context, "Generic failure.", Toast.LENGTH_SHORT).show();
                updateMsgType(uri, Sms.MESSAGE_TYPE_FAILED);
            } else if(resultCode == SmsManager.RESULT_ERROR_NO_SERVICE) {
                Toast.makeText(context, "service is currently unavailable.", Toast.LENGTH_SHORT).show();
                updateMsgType(uri, Sms.MESSAGE_TYPE_FAILED);
            } else if(resultCode == SmsManager.RESULT_ERROR_NULL_PDU) {
                Toast.makeText(context, "no pdu provided.", Toast.LENGTH_SHORT).show();
                updateMsgType(uri, Sms.MESSAGE_TYPE_FAILED);
            } else if(resultCode == SmsManager.RESULT_ERROR_RADIO_OFF) {
                Toast.makeText(context, "radio was explicitly turned off.", Toast.LENGTH_SHORT).show();
                updateMsgType(uri, Sms.MESSAGE_TYPE_FAILED);
            }
        }
    };
    IntentFilter filter = new IntentFilter(TxrjConstant.ACTION_SEND_SMS);
   mContext.registerReceiver(sentReceiver, filter);
}

private PendingIntent getSentIntent(final Uri uri) {
    if(sentReceiver == null) {
        createAndRegisterSentReceiver();
    }
    Intent sentIntent = new Intent(TxrjConstant.ACTION_SEND_SMS);
    sentIntent.putExtra(TxrjConstant.EXTRA_SENT_URI, uri);
    return PendingIntent.getBroadcast(mContext, 0, sentIntent, 0);
}

deliveryReceiver使用类似的处理方法。代码如下所示。

private void createAndRegisterDeliveryIntent() {
    deliveryReceiver = new BroadcastReceiver(){

        @Override
        public void onReceive(Context context, Intent intent) {
            mContext.unregisterReceiver(this);
            Toast.makeText(context, "message arrived.", Toast.LENGTH_SHORT).show();
        }
    };
    IntentFilter filter = new IntentFilter(TxrjConstant.ACTION_DELIVERY_SMS);
    mContext.registerReceiver(deliveryReceiver, filter);
}

private PendingIntent getDeliveryIntent() {
    if(deliveryReceiver == null) {
        createAndRegisterDeliveryIntent();
    }
    Intent deliveryIntent = new Intent(TxrjConstant.ACTION_DELIVERY_SMS);
    return PendingIntent.getBroadcast(mContext, 0, deliveryIntent, 0);
}

在onDestroy()方法中注销sentReceiver和deliveryReceiver。

protected void onDestroy() {
    super.onDestroy();
    getContentResolver().unregisterContentObserver(mInboxObserver);
    if(sentReceiver != null) {
        unregisterReceiver(sentReceiver);
    }
    if(deliveryReceiver != null) {
        unregisterReceiver(deliveryReceiver);
    }
}

MessageListActivity has leaked IntentReceiver的更多相关文章

  1. Android学习系列(37)--App调试内存泄露之Context篇(下)

    接着<Android学习系列(36)--App调试内存泄露之Context篇(上)>继续分析. 5. AsyncTask对象 我N年前去盛大面过一次试,当时面试官极力推荐我使用AsyncT ...

  2. [Android Memory] App调试内存泄露之Context篇(下)

    转载地址:http://www.cnblogs.com/qianxudetianxia/p/3655475.html 5. AsyncTask对象 我N年前去盛大面过一次试,当时面试官极力推荐我使用A ...

  3. Android 之 WebView

    1:在AndroidManifest.xml中添加允许android访问网络权限. <uses-permission android:name="android.permission. ...

  4. WebView全面学习(二)-- Native与js双方通信

    WebView全面学习(二)-- Native与js双方通信 Native与js通信的本质 Native与js通信的核心在于WebView. 两端的通信主要还是单向的.假如要完成js->Nati ...

  5. android中常见的内存泄漏和解决的方法

    android中的内存溢出预计大多数人在写代码的时候都出现过,事实上突然认为工作一年和工作三年的差别是什么呢.事实上干的工作或许都一样,产品汪看到的结果也都一样,那差别就是速度和质量了. 写在前面的一 ...

  6. StrictMode 详解

    StrictMode类是Android 2.3 (API 9)引入的一个工具类,可以用来帮助开发者发现代码中的一些不规范的问题.比如,如果你在UI线程中进行了网络或者磁盘操作,StrictMode就会 ...

  7. Activity has leaked window that was originally added

    错误: E/WindowManager: android.view.WindowLeaked: Activity com.x.x.x has leaked window com.android.int ...

  8. 数据库内存泄漏——A SQLiteConnection object for database '/data/data/.../databases/....db' was leaked!

      详细异常: A SQLiteConnection object for database '/data/data/.../database/....db' was leaked!  Please ...

  9. has leaked ServiceConnection com.baidu.location.LocationClient

    02-06 05:01:52.806: E/ActivityThread(1120): Activity com.project.xxxActivity $1@45fc5af8 that was or ...

随机推荐

  1. 基于libnids的TCP数据流的还原(多线程实现) .

    我们知道,libnids本身可以实现TCP数据流的重组,但是如果一个TCP流数据量比较大的时候,就会分成好多个TCP报文段,这些报文段在网络中的传播可能是乱序的,利用libnids可以帮助我们按顺序接 ...

  2. centos7 开机自动连网

    新安装好的CentOS7桌面版,默认的网络都是关闭的,在图形页面中,开启后,重启后网络又关闭了.下面配置开机自动连网. 工具/原料   CentOS7.2 方法/步骤     首先打开终端,用ifco ...

  3. Redis学习手册(主从复制)(转)

    一.Redis的Replication: 这里首先需要说明的是,在Redis中配置Master-Slave模式真是太简单了.相信在阅读完这篇Blog之后你也可以轻松做到.这里我们还是先列出一些理论性的 ...

  4. tensorflow项目构建流程

    https://blog.csdn.net/hjimce/article/details/51899683 一.构建路线 个人感觉对于任何一个深度学习库,如mxnet.tensorflow.thean ...

  5. capwap学习笔记——初识capwap(三)

    2.5.6 CAPWAP状态机详解 2.5.6.1 Start to Idle 这个状态变迁发生在设备初始化完成. ¢  WTP: 开启CAPWAP状态机.     ¢  AC:  开启CAPWAP状 ...

  6. 如何用Docker建立一个Node.js的开发环境

      建立一个文件夹 用管理员身份打开powershell. 在文件夹下面运行npm init, 根据提示填入信息,以便产生一个package.json文件. 在文件中加入需要的dependencies ...

  7. 阿里云centos配置nginx和nodejs

    今天新买了阿里云,想把网站跑起来,于是记录跑起来的过程 1.购买域名 2.购买解析 3.购买ecs主机 4.ssh登录主机 5.安装vsftpd 6.配置ftp用户.文件夹.权限 7.安装nginx/ ...

  8. javascript基于原型的语言的特点

    一.基于原型的语言的特点 1 只有对象,没有类;对象继承对象,而不是类继承类. 2  “原型对象”是基于原型语言的核心概念.原型对象是新对象的模板,它将自身的属性共享给新对象.一个对象不但可以享有自己 ...

  9. 第五周 Word注释与交叉引用

    第五周 Word注释与交叉引用 教学时间 2013-3-26 教学课时 2 教案序号 4 教学目标 1.掌握脚注.尾注.题注的概念和应用 2.掌握交叉引用的操作方法 教学过程: 复习提问 1.如何利用 ...

  10. ActiveMQ 基于zookeeper的主从(levelDB Master/Slave)搭建以及Spring-boot下使用

    0:说明 ActiveMQ 5.9.0新推出的主从实现,基于zookeeper来选举出一个master,其他节点自动作为slave实时同步消息.因为有实时同步数据的slave的存在,master不用担 ...