**
抱歉,这里的NoCopySpan慎用,可能有崩溃风险。
**
1 设置ClickableSpan导致内存泄漏
spannable.setSpan(new ClickableSpan() {
@Override
public void onClick(View widget) {
}
public void updateDrawState(TextPaint ds) {
ds.setColor(mContext.getResources().getColor();
ds.setUnderlineText(false);
}
}, start, start + tagNameMatch.length(), Spannable.SPAN_EXCLUSIVE_EXCLUSIVE);
导致内存泄漏的原因:
https://stackoverflow.com/questions/28539216/android-textview-leaks-with-setmovementmethod
Using ClickableSpan may still cause leaks even on versions higher than KitKat. If you look into implementation of the ClickableSpan you will notice that it doesn’t extend NoCopySpan, so it leaks in onSaveInstanceState() like described in @DmitryKorobeinikov and @ChrisHorner answers. So the solution would be to create a custom class that extends ClickableSpan and NoCopySpan.
解决办法也来自上面的网址:
public static class NoRefCopySpan extends ClickableSpan implements NoCopySpan{
@Override
public void onClick(@NonNull View widget) {
}
@Override
public void updateDrawState(TextPaint ds) {
super.updateDrawState(ds);
}
}
使用
spannable.setSpan(new NoRefCopySpan() {
@Override
public void onClick(View widget) {
}
public void updateDrawState(TextPaint ds) {
}
}, start, start + tagNameMatch.length(), Spannable.SPAN_EXCLUSIVE_EXCLUSIVE);

本文详细解析了在Android中使用TextView和ClickableSpan可能导致的内存泄漏问题,并提供了一种解决方案,即创建一个继承自ClickableSpan和NoCopySpan的自定义类,以避免在onSaveInstanceState()时发生的内存泄漏。

1737

被折叠的 条评论
为什么被折叠?



