android开发-bug记录

TUZILE

于 2022-01-11 14:46:03 发布

阅读量4k

点赞数

分类专栏： android开发文章标签： android java android studio bug

本文链接：https://blog.csdn.net/qq_42052656/article/details/122431660

版权

android开发专栏收录该内容

2 篇文章 0 订阅

订阅专栏

2022.01.10

正式接触android开发刚三四个月，记录一下三个第一次遇到的bug

自定义的圆角控件加载图片导致OOM

java.lang.OutOfMemoryError: Failed to allocate a 373980 byte allocation with 288904 free bytes and 282KB until OOM

// at dalvik.system.VMRuntime.newNonMovableArray(Native Method) // at android.graphics.Bitmap.nativeCreate(Native Method) // at android.graphics.Bitmap.createBitmap(Bitmap.java:879) // at android.graphics.Bitmap.createBitmap(Bitmap.java:856) // at android.graphics.Bitmap.createBitmap(Bitmap.java:776) // at com.discovery.modulehome.XCRoundRectImageView.getScaleBitmap(XCRoundRectImageView.java:221) // at com.discovery.modulehome.XCRoundRectImageView.onDraw(XCRoundRectImageView.java:92) // at android.view.View.draw(View.java:17320) // at android.view.View.updateDisplayListIfDirty(View.java:16259) // at android.view.View.draw(View.java:17070) // at android.view.ViewGroup.drawChild(ViewGroup.java:3892) // at android.view.ViewGroup.dispatchDraw(ViewGroup.java:3678) // at android.view.View.draw(View.java:17332) // at android.view.View.updateDisplayListIfDirty(View.java:16259) // at android.view.View.draw(View.java:17070) // at android.view.ViewGroup.drawChild(ViewGroup.java:3892) // at androidx.recyclerview.widget.RecyclerView.drawChild(RecyclerView.java:5204) // at android.view.ViewGroup.dispatchDraw(ViewGroup.java:3678) // at android.view.View.draw(View.java:17332) // at androidx.recyclerview.widget.RecyclerView.draw(RecyclerView.java:4603) // at android.view.View.updateDisplayListIfDirty(View.java:16259) // at android.view.ViewGroup.recreateChildDisplayList(ViewGroup.java:3876) // at android.view.ViewGroup.dispatchGetDisplayList(ViewGroup.java:3856) // at android.view.View.updateDisplayListIfDirty(View.java:16213) // at android.view.ViewGroup.recreateChildDisplayList(ViewGroup.java:3876) // at android.view.ViewGroup.dispatchGetDisplayList(ViewGroup.java:3856) // at android.view.View.updateDisplayListIfDirty(View.java:16213) // at android.view.ViewGroup.recreateChildDisplayList(ViewGroup.java:3876) // at android.view.ViewGroup.dispatchGetDisplayList(ViewGroup.java:3856) // at android.view.View.updateDisplayListIfDirty(View.java:16213) // at android.view.ViewGroup.recreateChildDisplayList(ViewGroup.java:3876) // at android.view.ViewGroup.dispatchGetDisplayList(ViewGroup.java:3856) // at android.view.View.updateDisplayListIfDirty(View.java:16213) // at android.view.ViewGroup.recreateChildDisplayList(ViewGroup.java:3876) // at android.view.ViewGroup.dispatchGetDisplayList(ViewGroup.java:3856) // at android.view.View.updateDisplayListIfDirty(View.java:16213) // at android.view.ViewGroup.recreateChildDisplayList(ViewGroup.java:3876) // at android.view.ViewGroup.dispatchGetDisplayList(ViewGroup.java:3856) // at android.view.View.updateDisplayListIfDirty(View.java:16213) // at android.view.ViewGroup.recreateChildDisplayList(ViewGroup.java:3876) // at android.view.ViewGroup.dispatchGetDisplayList(ViewGroup.java:3856) // at android.view.View.updateDisplayListIfDirty(View.java:16213) // at android.view.ViewGroup.recreateChildDisplayList(ViewGroup.java:3876) // at android.view.ViewGroup.dispatchGetDisplayList(ViewGroup.java:3856) // at android.view.View.updateDisplayListIfDirty(View.java:16213) // at android.view.ViewGroup.recreateChildDisplayList(ViewGroup.java:3876) // at android.view.ViewGroup.dispatchGetDisplayList(ViewGroup.java:3856) // at android.view.View.updateDisplayListIfDirty(View.java:16213) // at android.view.ViewGroup.recreateChildDisplayList(ViewGroup.java:3876) // at android.view.ViewGroup.dispatchGetDisplayList(ViewGroup.java:3856) // at android.view.View.updateDisplayListIfDirty(View.java:16213) // at android.view.ViewGroup.recreateChildDisplayList(ViewGroup.java:3876) // at android.view.ViewGroup.dispatchGetDisplayList(ViewGroup.java:3856) // at android.view.View.updateDisplayListIfDirty(View.java:16213) // at android.view.ViewGroup.recreateChildDisplayList(ViewGroup.java:3876) // at android.view.ViewGroup.dispatchGetDisplayList(ViewGroup.java:3856) // at android.view.View.updateDisplayListIfDirty(View.java:16213) // at android.view.ViewGroup.recreateChildDisplayList(ViewGroup.java:3876) // at android.view.ViewGroup.dispatchGetDisplayList(ViewGroup.java:3856) // at android.view.View.updateDisplayListIfDirty(View.java:16213) // at android.view.ViewGroup.recreateChildDisplayList(ViewGroup.java:3876) // at android.view.ViewGroup.dispatchGetDisplayList(ViewGroup.java:3856) // at android.view.View.updateDisplayListIfDirty(View.java:16213) // at android.view.ViewGroup.recreateChildDisplayList(ViewGroup.java:3876) // at android.view.ViewGroup.dispatchGetDisplayList(ViewGroup.java:3856) // at android.view.View.updateDisplayListIfDirty(View.java:16213) // at android.view.ThreadedRenderer.updateViewTreeDisplayList(ThreadedRenderer.java:661) // at android.view.ThreadedRenderer.updateRootDisplayList(ThreadedRenderer.java:667) // at android.view.ThreadedRenderer.draw(ThreadedRenderer.java:775) // at android.view.ViewRootImpl.draw(ViewRootImpl.java:3188) // at android.view.ViewRootImpl.performDraw(ViewRootImpl.java:2981) // at android.view.ViewRootImpl.performTraversals(ViewRootImpl.java:2569) // at android.view.ViewRootImpl.doTraversal(ViewRootImpl.java:1462) // at android.view.ViewRootImpl$TraversalRunnable.run(ViewRootImpl.java:6965) // at android.view.Choreographer$CallbackRecord.run(Choreographer.java:907) // at android.view.Choreographer.doCallbacks(Choreographer.java:709) // at android.view.Choreographer.doFrame(Choreographer.java:644) // at android.view.Choreographer$FrameDisplayEventReceiver.run(Choreographer.java:893) // at android.os.Handler.handleCallback(Handler.java:836) // at android.os.Handler.dispatchMessage(Handler.java:103) // at android.os.Looper.loop(Looper.java:203) // at android.app.ActivityThread.main(ActivityThread.java:6251) // at java.lang.reflect.Method.invoke(Native Method) // at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:1063) // at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:924)

解：

根据网络上别人的经验，确认是在列表中上拉加载很多数据的时候，由于列表中的item含有一个自定义的圆角图片（继承ImageView的自定义圆角控件）导致的。

解决方式：需要在清单文件的application中加上下面两行代码：

 android:largeHeap="true"
 android:hardwareAccelerated="false"

android:largeHeap

在manifest中设置了 largeHeap=true之后，可以使用最大内存值。设置largeHeap的确可以增加内存的申请量。但不是系统有多少内存就可以申请多少，而是由dalvik.vm.heapsize限制。但是作为程序员的我们应该努力减少内存的使用，尽量想回收和复用的方法，而不是想方设法增大内存。当内存很大的时候，每次gc的时间也会长一些，性能会下降的。

android:hardwareAccelerated

通过网络得知：从Android3.0 (API level11)开始，Android的2D显示管道被被设计得更加支持硬加速了。硬加速使用GPU承担了所有在View的canvas上执行的绘制操作。启用硬加速最简单的的方法是对整个应用启用硬件速。如果应用只使用标准的view和Drawable，全局启用硬加速将不会带来任何负面影响。然而，因为硬加速不是被所有的２Ｄ绘制所支持，所以启用它时可能对自定义绘制产生影响。出现的问题经常是不可见的，也可能是异常，或错误地显示了像素。

而我这儿因为使用了自定义视频控件，添加了上面两个属性导致视频一致未准备好surface。尝试在AndroidManifest.xml中，用android:replace去覆盖属性值，但是无效（也有可能我使用的方式不太对，小白菜无奈..）。最后还是把所有使用了自定义的圆角图片控件的地方，换成通过继承Gilde的自定义对象，在java代码中动态加载图片切圆角。然后就不报这个bug了，视频也正常。

终：

与视频的绘制冲突，填上会导致视频surface一直未准备好

还是换掉自定义控件去解决。

弹窗导致IllegalStateException：报not associated with a fragment manager.错误

CRASH: com.discovery.home.launcher.fj01 (pid 2999) // Short Msg: java.lang.IllegalStateException // Long Msg: java.lang.IllegalStateException: Fragment SYDialog{7b91deb (f60f3e52-b3e8-49f7-bcaf-13b4f6dd5700)} not associated with a fragment manager.

// Build Label: alps/full_fj01/fj01:7.0/NRD90M/1641551929:user/test-keys // Build Changelist: 1641551929 // Build Time: 1641551927000 // java.lang.IllegalStateException: Fragment SYDialog{7b91deb (f60f3e52-b3e8-49f7-bcaf-13b4f6dd5700)} not associated with a fragment manager. // at androidx.fragment.app.Fragment.requireFragmentManager(Fragment.java:910) // at androidx.fragment.app.DialogFragment.dismissInternal(DialogFragment.java:245) // at androidx.fragment.app.DialogFragment.dismissAllowingStateLoss(DialogFragment.java:212) // at com.discovery.modulehome.first_level.HomeWorkFragment.initTime(HomeWorkFragment.java:840) // at com.discovery.modulehome.first_level.HomeWorkFragment.access$3300(HomeWorkFragment.java:63) // at com.discovery.modulehome.first_level.HomeWorkFragment$1.handleMessage(HomeWorkFragment.java:522) // at android.os.Handler.dispatchMessage(Handler.java:110) // at android.os.Looper.loop(Looper.java:203) // at android.app.ActivityThread.main(ActivityThread.java:6251) // at java.lang.reflect.Method.invoke(Native Method) // at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:1063) // at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:924)

解：SYDialog是自定义的弹窗，是前辈写的通用工具，继承了DialogFragment。

dismiss()方法会调用dismissInternal方法,dismissInternal方法中需要获取mFragmentManager，如果为null就会抛出异常。在调用DialogFragment的时候需要传入一个FragmentMananger或是一个FragmentTransaction，并且把自身add到FragmentTransaction中，这时DialogFragment的mFragmentManager就被赋值了

根据网络的经验，和自己所做项目的特点，确认是fragment还没有初始化好，传入的getFragmentManager()值为null所导致。

解决方法：避免在没有DialogFramgent没有show过的情况下调用dismiss 或是重写dismiss方法，手动判断在mFragmentManager不为null时才dismiss。所以添加了判空保护。

Glide加载图片时界面分离UI，导致NullPointerException

Short Msg: java.lang.NullPointerException // Long Msg: java.lang.NullPointerException: You cannot start a load on a not yet attached View or a Fragment where getActivity() returns null (which usually occurs when getActivity() is called before the Fragment is attached or after the Fragment is destroyed).

// Build Label: alps/full_fj01/fj01:7.0/NRD90M/1641551929:user/test-keys // Build Changelist: 1641551929 // Build Time: 1641551927000 // java.lang.NullPointerException: You cannot start a load on a not yet attached View or a Fragment where getActivity() returns null (which usually occurs when getActivity() is called before the Fragment is attached or after the Fragment is destroyed). // at com.bumptech.glide.util.Preconditions.checkNotNull(Preconditions.java:29) // at com.bumptech.glide.Glide.getRetriever(Glide.java:769) // at com.bumptech.glide.Glide.with(Glide.java:838) // at com.discovery.librarybase.imageloader.glide.GlideLoader.request(GlideLoader.java:28) // at com.discovery.librarybase.imageloader.ImageLoaderConfig.request(ImageLoaderConfig.java:37) // at com.discovery.librarybase.imageloader.ImageLoaderConfig$Builder.into(ImageLoaderConfig.java:109) // at com.test.moduleuser.fragment.UserCenterFragment.setHeadPicture(UserCenterFragment.java:156) // at com.test.moduleuser.fragment.UserCenterFragment.access$500(UserCenterFragment.java:36) // at com.test.moduleuser.fragment.UserCenterFragment$2.handleMessage(UserCenterFragment.java:76) // at android.os.Handler.dispatchMessage(Handler.java:110) // at android.os.Looper.loop(Looper.java:203) // at android.app.ActivityThread.main(ActivityThread.java:6251) // at java.lang.reflect.Method.invoke(Native Method) // at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:1063) // at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:924)

解：

Glide加载图片报错，可能是activity被销毁，而getContext()传入了空值导致的。我的页面都是fragment，加载前使用this.isDetached()判断页面是否分离ui。

希望自己日益精进。

2022.01.11