Skip to content

Memory leaks occur when an activity is destroyed and recreated. Android os #173770

Closed
#175937
Closed
Memory leaks occur when an activity is destroyed and recreated. Android os#173770
#175937
Assignees
camsim99
Labels
P1High-priority issues at the top of the work listc: performanceRelates to speed or footprint issues (see "perf:" labels)engineflutter/engine related. See also e: labels.found in release: 3.33Found to occur in 3.33found in release: 3.35Found to occur in 3.35frameworkflutter/packages/flutter repository. See also f: labels.has reproducible stepsThe issue has been confirmed reproducible and is ready to work onperf: memoryPerformance issues related to memoryplatform-androidAndroid applications specificallyr: fixedIssue is closed as already fixed in a newer versionteam-androidOwned by Android platform teamtriaged-androidTriaged by Android platform team

Description

@SJLBenjamin
SJLBenjamin
opened on Aug 14, 2025

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

Image

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

Activity

  1. tirth-patel-nc
    added
    in triagePresently being triaged by the triage team
    on Aug 14, 2025

  2. tirth-patel-nc commented on Aug 14, 2025

    @tirth-patel-nc
    tirth-patel-nc
    on Aug 14, 2025
    Member

    @SJLBenjamin Report seems vague. For us to further investigate this issue, please provide a completed and minimal reproducible code sample that doesn’t include 3rd party plugins or complex production code. Also, please share the output flutter doctor -v. Thank you!

  3. tirth-patel-nc
    added
    waiting for responseThe Flutter team cannot make further progress on this issue until the original reporter responds
    on Aug 14, 2025

  4. SJLBenjamin commented on Aug 15, 2025

    @SJLBenjamin
    SJLBenjamin
    on Aug 15, 2025
    Author

    @SJLBenjamin Report seems vague. For us to further investigate this issue, please provide a completed and minimal reproducible code sample that doesn’t include 3rd party plugins or complex production code. Also, please share the output flutter doctor -v. Thank you!

    example:
    memorydemosjl.zip

    flutter doctor -v:

    Image

  5. github-actions
    removed
    waiting for responseThe Flutter team cannot make further progress on this issue until the original reporter responds
    on Aug 15, 2025

  6. tirth-patel-nc commented on Aug 15, 2025

    @tirth-patel-nc
    tirth-patel-nc
    on Aug 15, 2025
    Member

    @SJLBenjamin please confirm whether #145750, #168658 are related to your case

  7. tirth-patel-nc
    added
    waiting for responseThe Flutter team cannot make further progress on this issue until the original reporter responds
    on Aug 15, 2025

  8. SJLBenjamin commented on Aug 15, 2025

    @SJLBenjamin
    SJLBenjamin
    on Aug 15, 2025
    Author

    @SJLBenjamin please confirm whether #145750, #168658 are related to your case

    It should not be related to me, because after creating the project with Android studio, the code has not been changed, and I have the necessary path

  9. github-actions
    removed
    waiting for responseThe Flutter team cannot make further progress on this issue until the original reporter responds
    on Aug 15, 2025

  10. tirth-patel-nc commented on Aug 18, 2025

    @tirth-patel-nc
    tirth-patel-nc
    on Aug 18, 2025
    Member

    Thanks for the update. I'm observing the same behaviour on the latest SDK versions.

    I enabled Don't keep activities in Developer options and tested it on both an emulator and a physical android device.

    stable : 3.32.8, 3.35.1
master : 3.33.0-1.0.pre-1457
beta : 3.36.0-0.1.pre
    Image Image

    so it looks similar to #23181, but that one is too old to be a valid reference in this case.

  11. tirth-patel-nc
    added
    platform-androidAndroid applications specifically
    has reproducible stepsThe issue has been confirmed reproducible and is ready to work on
    found in release: 3.33Found to occur in 3.33
    found in release: 3.35Found to occur in 3.35
    and removed
    in triagePresently being triaged by the triage team
    on Aug 18, 2025

  12. 14 remaining items

  13. reidbaker
    assigned
    camsim99
    and unassigned
    reidbaker
    on Sep 5, 2025

  14. liweiGe commented on Sep 16, 2025

    @liweiGe
    liweiGe
    on Sep 16, 2025
    Image I used this code to temporarily solve it, but I still have to wait for the SDK to be updated.
  15. github-merge-queue
    added a commit that references this issue on Oct 16, 2025

    [Android] Refactor `ImageReaderSurfaceProducer` restoration after app…

    8ee908d
  16. auto-submit
    closed this as completedin #175937on Oct 16, 2025
  17. tirth-patel-nc
    added
    r: fixedIssue is closed as already fixed in a newer version
    on Oct 16, 2025
  18. flutteractionsbot
    added 2 commits that reference this issue on Oct 16, 2025

    [Android] Refactor `ImageReaderSurfaceProducer` restoration after app…

    2911fe7

    [Android] Refactor `ImageReaderSurfaceProducer` restoration after app…

    dfd26b1
  19. camsim99
    added a commit that references this issue on Oct 16, 2025

    [Android] Refactor `ImageReaderSurfaceProducer` restoration after app…

    a134b81
  20. auto-submit
    added 2 commits that reference this issue on Oct 21, 2025

    [CP-stable][Android] Refactor `ImageReaderSurfaceProducer` restoratio…

    0353165

    [CP-beta][Android] Refactor `ImageReaderSurfaceProducer` restoration …

    53f2819

  21. github-actions commented on Oct 30, 2025

    @github-actions
    github-actionsbot
    on Oct 30, 2025 – with GitHub Actions

    This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of flutter doctor -v and a minimal reproduction of the issue.

  22. github-actions
    locked as resolved and limited conversation to collaborators on Oct 30, 2025
  23. reidbaker
    added a commit that references this issue on Dec 10, 2025

    [Android] Refactor `ImageReaderSurfaceProducer` restoration after app…

    956967f
  24. Nakiha
    added a commit that references this issue on Sep 28, 2026

    [Android] Refactor `ImageReaderSurfaceProducer` restoration after app…

    f2c4d57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

P1High-priority issues at the top of the work listc: performanceRelates to speed or footprint issues (see "perf:" labels)engineflutter/engine related. See also e: labels.found in release: 3.33Found to occur in 3.33found in release: 3.35Found to occur in 3.35frameworkflutter/packages/flutter repository. See also f: labels.has reproducible stepsThe issue has been confirmed reproducible and is ready to work onperf: memoryPerformance issues related to memoryplatform-androidAndroid applications specificallyr: fixedIssue is closed as already fixed in a newer versionteam-androidOwned by Android platform teamtriaged-androidTriaged by Android platform team

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions