Skip to content

There should be clarity and guidance on to address disposal of objects in exceptional situations. #157470

@polina-c

Description

@polina-c

Exceptional code paths should be finalized properly and should not result in leaking objects.

Some flutter tests are opted out from leak tracking because of exceptions.
And it is not clear if it is valid opt out.
Leak tracker may be can detect if exception happened and skip flagging not disposed objects for valid stories.

Search for // leaking by design because of exception in code of flutter framework.

Metadata

Metadata

Assignees

No one assigned

    Labels

    P3Issues that are less important to the Flutter projecta: leak trackingIssues and PRs related to memory leaks detected by leak_trackerframeworkflutter/packages/flutter repository. See also f: labels.team-frameworkOwned by Framework teamtriaged-frameworkTriaged by Framework team

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions