Android-FloatWindow MEMORY LEAK

MEMORY LEAK

Open deerclops opened this issue 5 years ago • 6 comments

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

Sep 12 '18 07:09 deerclops

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.