Android EditText 内存泄漏

时间:2023-03-25
本文介绍了Android EditText 内存泄漏的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着跟版网的小编来一起学习吧!

问题描述

很多人注意到活动中的 EditText 持有对活动的强引用,即使它完成后也是如此.要清楚,此 EditText 位于布局内并膨胀,没有设置 Listeners.这只发生在某些设备上,例如三星 Galaxy S4 (Android 4.2.2) 等.许多关于此的帖子仍然没有解决方案.首先是一些有用的帖子.(最终 GC 会清除它,因此从技术上讲它不是泄漏,但对于内存大的应用程序来说,它需要很长时间并且会导致 OOM)

Alot of people are noticing EditText in an activity is holding a Strong Reference to an Activity even once its finished. To be clear this EditText is inside a layout and inflated, there is no Listeners set. This only happens on certain devices e.g. Samsung Galaxy S4 (Android 4.2.2) and others. Many post about this still no solution. First here is some useful posts. (Eventually GC will clean this so its not technically a leak, but for heavy memory apps it takes way to long and will cause OOM)

Android Samsung Memory leak in EditText

Why does EditText retain its Activity's Context in Ice Cream Sandwich

EditText causing memory leak

Possibility of unhandled memory leak

The solutions noted do not work for all devices. It comes down to the Edittext Watcher. I think there may be solution in overriding this Watcher then having a function to clean it up onDestroy(). Please any help here, I been at this for days.

Here is the MAT Histogram

解决方案

It is because EditText references the context of Activity. When the Activity is destroyed, Activity cannot be recycled normally because Edittext holds a reference to the context of activity. Solution: Rewrite EditText, change the reference to the Context in Activity to the reference to ApplicationContext.

Instructions:

https://programming.vip/docs/solve-the-memory-leak-problem-caused-by-edittext-in-android.html

这篇关于Android EditText 内存泄漏的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持跟版网!

上一篇:在 Android 视图中使用 UI 元素进行测试 下一篇:EditText 的 onCreateContextMenu() 在真实设备上不起作用

相关文章