为什么添加和删除片段会给我造成内存泄漏？
[英]Why is adding and removing a fragment giving me memory leak?
问题描述
I am fairly new to android dev so any help is really appreciated! 
我对android开发人员还很陌生，因此非常感谢您的帮助！ I am getting this error 我收到此错误
12-30 08:14:32.391 1726-1741/?
and part of the code that's causing the error 以及导致错误的部分代码
gameLayout.setOnTouchListener(
new FrameLayout.OnTouchListener() {
@Override
public boolean onTouch(View v, MotionEvent event) {
//add bullet upon click
bullet_fragment b_fragment = new bullet_fragment();
fragmentTransaction.add(R.id.game, b_fragment).commit();
//bullet moves around screen (some code here)
// removes bullet
fragmentTransaction.remove(b_fragment).commit();
return true;
}
g }
);
so every time the screen is touched a fragment is generated so it's possible for there to be multiples of the same fragment to exist on the screen, which is no problem I've tried searching a bit and found that remove() doesn't necessarily move the fragment to the GC, but the person didn't say how to completely destroy it. 因此，每次触摸屏幕时都会生成一个片段，因此屏幕上可能存在多个相同片段，这是我尝试搜索一下并发现remove（）不一定有问题的问题将该碎片移至GC，但此人没有透露如何完全销毁它。 How can I do that then? 那我该怎么办呢？ or is there another reason for that error to occur? 还是有其他原因导致该错误发生？
code of the fragment 片段代码
public class bullet_fragment extends Fragment {
View bulletView;
ImageView bulletObject;
@Override
public View onCreateView(LayoutInflater inflater, ViewGroup container, Bundle savedInstanceState) {
bulletView = inflater.inflate(R.layout.bullet_layout, container, true);
bulletObject = (ImageView) bulletView.findViewById(R.id.bullet);
return bulletView;
}
public void shoot(int x, int y){
FrameLayout.LayoutParams b_params = new FrameLayout.LayoutParams(bulletObject.getLayoutParams());
final int B_WIDTH= (int) (bulletObject.getWidth() * 0.5);
final int B_HEIGHT= (int) (bulletObject.getHeight() * 0.5);
b_params.setMargins(x - B_WIDTH,y - B_HEIGHT,0,0);
bulletObject.setLayoutParams(b_params);
}
} }
1 个解决方案
解决方案1
0 已采纳 2015-12-30 04:15:56
The issue in the stacktrace is clearly caused by okhttp but it may not necessarily be the fault of okhttp. 堆栈跟踪中的问题显然是由okhttp引起的，但不一定是okhttp的错误。 The fact that this happens inside gms which is part of Google Services suggests that you likely have nothing to do with the issue. 这是Google Services的一部分gms内部发生的事实，这表明您可能与该问题无关。 Are you sure this log is for your process and not some system process? 您确定此日志用于您的进程而不是某些系统进程吗？
okhttp reference okhttp参考
picasso reference (as an example of how a library may be at fault) 毕加索参考资料（作为图书馆可能出现故障的示例）
声明:本站的技术帖子网页，遵循CC BY-SA 4.0协议，如果您需要转载，请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.