-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
老板,内存泄漏了 #436
Comments
我也遇到这个问题 |
我也遇到 |
1 similar comment
我也遇到 |
求解决啊老板 |
求解决啊 |
RequestExecutor
mMessage 和 mRequest 持有了Context ,后续没有权限请求之后没有置空导致的泄漏,这里置空解决。 |
求解决 |
+1 |
2.0.2版本大概什么时候Release呢 |
1 similar comment
2.0.2版本大概什么时候Release呢 |
2.0.2版本大概什么时候Release |
感觉差不多就可以发一版了,这个内存泄露老是出来。 |
我也遇到了这个内存泄漏,请问v2.0.2的Release大概什么时候发布呢? |
mark一下,期待2.0.2版本严大神的开源库还是挺不错的 |
2.0.3版本依然报出这个问题 |
作者你好,我用的是2.0.1的support包,加了 mMessenger = null;mRequest = null;这两行代码,可是还是报内存泄露,啥原因啊 |
这样加了,我看还是会报呢 |
我改了两处,一个onCallback处mMessenger = null; mRequest = null; 另一个 mMessenger = new Messenger(mRequest.getSource().getContext(), this);改成mMessenger = new Messenger(mRequest.getSource().getContext().getApplicationContext(), this); 现在是没有泄露了,试了下这两处少任何一处都会有内存泄露,不知道为啥要改第二处 |
Instance of com.yanzhenjie.permission.bridge.RequestExecutor 就是这个线程造成的
The text was updated successfully, but these errors were encountered: