Skip to content
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

MEMORY LEAK #3

Open
deerclops opened this issue Sep 12, 2018 · 6 comments
Open

MEMORY LEAK #3

deerclops opened this issue Sep 12, 2018 · 6 comments

Comments

@deerclops
Copy link

The single instance FloatWindow retains the reference to a context passed from getFloatWindow() method.

In your sample module, after the activity created the FloatWindow is finished, the activity can not be recycled when GC is triggered, which will cause memory leak.

default

@YoungBill
Copy link
Owner

Ok, first of all thank you very much for your feedback.
When I have time, I will optimize the memory leak as soon as possible.
If you have time, welcome your repair submission.

@iielse
Copy link

iielse commented Oct 9, 2018

俩Chinese用英语交流。

@YoungBill
Copy link
Owner

hhh

@AB901
Copy link

AB901 commented Jan 11, 2019

大佬,我想付学费学习这个,刚从PHP转安卓,理解上有点吃力,不知是否愿意授课

@AB901
Copy link

AB901 commented Jan 11, 2019

我是说,学习怎么引用你这个类........

@YoungBill
Copy link
Owner

可以授课得

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants