It looks like the memory management release problem of the flutter itself, even if the image cache is released on the page

The reason is that the old version of flutter has problems in caching and recycling the high-resolution images loaded by GridView and listview components, which leads to the memory explosion and cannot be recycled automatically. It is also impossible to manually turn off the cache and clear the image cache. The official solved this problem in the latest master branch code, and the memory consumption did not fluctuate significantly when loading images

Solution:

And I will not merge to the 1.9.1 otfix branch. We can only wait for the latest stable version, or change a version by ourselves

Similar Posts:

• You have not completed the merge: You have not concluded your merge (MERGE_HEAD exists)
• [Solved] Compile Error: virtual memory exhausted: Cannot allocate memory
• Git pull does not specify an error message for the branch
• Setting up CocoaPods master repo [How to Fix Stuck Issue]
• Git you are not allowed to push code to protected branches on this project?
• A rejected – non fast forward error occurred in eclipse push
• [Solved] Git pull fatal: refusing to merge unrelated histories
• A rejected – non fast forward error occurred in eclipse push
• Git – Your branch and ‘origin/xxx’ have diverged