Memory leaks occur when an activity is destroyed and recreated. Android os #173770
Description
Note
For anyone looking at this issue now, this leak was introduced by 233edc0 in Flutter 3.29.
1.Create a Flutter project using Android Studio.
2.Enter the developer options, set not to keep activities, (destroy each activity as soon as the user leaves it)
3.Entering the activity, clicking the home button, exiting the activity, and then entering the activity again will trigger the destruction and reconstruction of the activity.
4.Check memory leaks through profiler and find memory leaks
5.In actual use, the same problem will occur if the system kills the activity due to insufficient memory.
6.The same problem occurred with 3.27.1 and 3.32.8
Metadata
Metadata
Assignees
Labels
High-priority issues at the top of the work listRelates to speed or footprint issues (see "perf:" labels)flutter/engine related. See also e: labels.Found to occur in 3.33Found to occur in 3.35flutter/packages/flutter repository. See also f: labels.The issue has been confirmed reproducible and is ready to work onPerformance issues related to memoryAndroid applications specificallyIssue is closed as already fixed in a newer versionOwned by Android platform teamTriaged by Android platform team