Skip to content
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

No way to see what references leaked instance #3424

Closed
AAverin opened this issue Oct 4, 2021 · 2 comments
Closed

No way to see what references leaked instance #3424

AAverin opened this issue Oct 4, 2021 · 2 comments
Labels
screen: memory Issues with the Memory screen.

Comments

@AAverin
Copy link

AAverin commented Oct 4, 2021

In Android the common way to find a leak is to:

  • find which instance is leaking by finding duplicates (for example)
  • switching to the references view and finding which other instance is still holding reference to our leaking instance

Such analysis is not possible in devtools for Flutter because it's not possible to see who/what references the instance.

@kenzieschmoll kenzieschmoll added the screen: memory Issues with the Memory screen. label Oct 4, 2021
@kenzieschmoll
Copy link
Member

@terrylucas

@polina-c
Copy link
Contributor

Duplicate to #3951

@polina-c polina-c closed this as not planned Won't fix, can't repro, duplicate, stale May 20, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
screen: memory Issues with the Memory screen.
Projects
None yet
Development

No branches or pull requests

3 participants