You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 22, 2022. It is now read-only.
I think if the screenshot already recycle before created new screenshot, the memory can not be out when flip many time because it's de-allocate after recycle(). I mean maybe created and recycle bitmap is not the reason of OOM error, maybe the reason is: Somethings goes bigger after each flipping -> OOM errors.
The issue is about to reduce the risk, not to avoid it.
I analyzed the heap status after flipping 100+ pages. There is no bitmap instances or other objects leaking. Then I thought OOM is caused by the behavior of adapter.
Please refer to #33, I will push a fix in a minute
Bitmap instances are constantly created and recycled during flipping.
Implementing a bitmap cache could improve performance and reduce the risk of OOM errors.
The text was updated successfully, but these errors were encountered: