android – PopupMenu PopupWindow $PopupViewContainer泄漏
作者:互联网
我有一个PopupMenu锚定到Action Bar中的一个按钮,我正在获取有关泄漏窗口的日志输出.
如果在PopupMenu打开时我的活动停止,则会发生这种情况.
我发布了一个相关问题here,但我已经解决了这个问题.
我见过一些类似的问题,比如this,但没有一个与PopupMenu有关.
我想我是否可以在提到的PopupWindow $PopupViewContainer上获得一个句柄,然后我可以在onPause或类似的东西中从WindowManager中删除它,但我不知道如何得到它. PopupMenu公开的界面非常有限.
>有没有人遇到过这个问题?
>有没有人修理过它或者解决它?
>有人知道如何获得PopupMenu的视图或窗口吗?
这就是我创建菜单的方法:
// in Activity
@Override
public boolean onCreateOptionsMenu(Menu menu) {
super.onCreateOptionsMenu(menu);
final MenuInflater inflater = getMenuInflater();
inflater.inflate(R.menu.main_menu, menu);
MenuItem login = menu.findItem(R.id.menu_login);
final Button button = (Button) login.getActionView().findViewById(R.id.login);
button.setOnClickListener(new View.OnClickListener() {
public void onClick(View item) {
if (profileMenu == null) {
// I've tried passing getApplicationContext() here too, with no change
profileMenu = new PopupMenu(ListActivity.this, button);
profileMenu.getMenuInflater().inflate(R.menu.profile_menu, profileMenu.getMenu());
profileMenu.setOnMenuItemClickListener(new PopupMenu.OnMenuItemClickListener() {
public boolean onMenuItemClick(MenuItem item) {
// there was code here, but I removed it and problem persists
return false;
}
});
}
profileMenu.show();
}
});
这是完整的堆栈跟踪:
10-24 11:10:13.878: E/WindowManager(2048): Activity **.app.ListActivity has leaked window android.widget.PopupWindow$PopupViewContainer@4157a7e8 that was originally added here
10-24 11:10:13.878: E/WindowManager(2048): android.view.WindowLeaked: Activity **.app.ListActivity has leaked window android.widget.PopupWindow$PopupViewContainer@4157a7e8 that was originally added here
10-24 11:10:13.878: E/WindowManager(2048): at android.view.ViewRootImpl.<init>(ViewRootImpl.java:374)
10-24 11:10:13.878: E/WindowManager(2048): at android.view.WindowManagerImpl.addView(WindowManagerImpl.java:292)
10-24 11:10:13.878: E/WindowManager(2048): at android.view.WindowManagerImpl.addView(WindowManagerImpl.java:224)
10-24 11:10:13.878: E/WindowManager(2048): at android.view.WindowManagerImpl$CompatModeWrapper.addView(WindowManagerImpl.java:149)
10-24 11:10:13.878: E/WindowManager(2048): at android.widget.PopupWindow.invokePopup(PopupWindow.java:988)
10-24 11:10:13.878: E/WindowManager(2048): at android.widget.PopupWindow.showAsDropDown(PopupWindow.java:897)
10-24 11:10:13.878: E/WindowManager(2048): at android.widget.ListPopupWindow.show(ListPopupWindow.java:595)
10-24 11:10:13.878: E/WindowManager(2048): at com.android.internal.view.menu.MenuPopupHelper.tryShow(MenuPopupHelper.java:127)
10-24 11:10:13.878: E/WindowManager(2048): at com.android.internal.view.menu.MenuPopupHelper.show(MenuPopupHelper.java:100)
10-24 11:10:13.878: E/WindowManager(2048): at android.widget.PopupMenu.show(PopupMenu.java:108)
10-24 11:10:13.878: E/WindowManager(2048): at **.app.ListActivity$3.onClick(ListActivity.java:376)
10-24 11:10:13.878: E/WindowManager(2048): at android.view.View.performClick(View.java:4084)
10-24 11:10:13.878: E/WindowManager(2048): at android.view.View$PerformClick.run(View.java:16966)
10-24 11:10:13.878: E/WindowManager(2048): at android.os.Handler.handleCallback(Handler.java:615)
10-24 11:10:13.878: E/WindowManager(2048): at android.os.Handler.dispatchMessage(Handler.java:92)
10-24 11:10:13.878: E/WindowManager(2048): at android.os.Looper.loop(Looper.java:137)
10-24 11:10:13.878: E/WindowManager(2048): at android.app.ActivityThread.main(ActivityThread.java:4745)
10-24 11:10:13.878: E/WindowManager(2048): at java.lang.reflect.Method.invokeNative(Native Method)
10-24 11:10:13.878: E/WindowManager(2048): at java.lang.reflect.Method.invoke(Method.java:511)
10-24 11:10:13.878: E/WindowManager(2048): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:786)
10-24 11:10:13.878: E/WindowManager(2048): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:553)
10-24 11:10:13.878: E/WindowManager(2048): at dalvik.system.NativeStart.main(Native Method)
解决方法:
简单地调用profileMenu.dismiss()onStop()就足够了.
标签:popupmenu,android,memory-leaks 来源: https://codeday.me/bug/20191006/1860754.html