-
Notifications
You must be signed in to change notification settings - Fork 55
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
after hot restart serveral time while debuging will cause crash #14
Comments
It seems that the native cannot release the image memory due to hot restart, so the memory continues to increase, which eventually leads to OOM. This problem only occurs when the renderingType is texture. Normally, when imageCache removes imageProvider, PowerImage will notify native to release memory. But when hot restart these processes are gone. I'm guessing something similar to this issue: |
thanks for your reply,dose it will be work if execute clean image cache every time at the begin of run my app. like this
|
This should be useless. At this time, the hot restart has ended, and the ImageCache must be empty. The problem is that native doesn't perceive hot restart, so it never releases textures. |
so as long as we can not reach the hot restart begin,this issue will always exists, right? Is there anything else we still can do.🫣 |
Describe the bug
after hot restart serveral time while debuging will cause crash,I have encountered this issue for many time.
sometimes the log show out of memory,but this time show like as below
To Reproduce
Steps to reproduce the behavior:
configured like the test demo and have replace most of image widget with power_image;
Expected behavior
please dont crash that often 😅,
Screenshots

If applicable, add screenshots to help explain your problem.
Versions (please complete the following information):
flutter doctor -v
:展开查看 flutter doctor details
Additional context
The text was updated successfully, but these errors were encountered: