Parent classes in memory profiler

[jacob314]

This issue was originally filed as dart-lang/sdk#39200

@BharathMG wrote:

Hey guys,
When I use memory profiler in dev tools, it is impossible to find which class is responsible for leaking dart and flutter objects. For ex, when I scroll the flutter list, I see a dart hidden class _List memory keeps growing. And I find no way to track down the parent class responsible for leaking those dart objects.What is the recommended way to find memory leak issues using memory profiler?

[jacob314]

Fyi @terrylucas

[venkatesh-sharechat]

Any luck on being to move this forward? Extremely hard to debug issues caused on the framework code.

[jacob314]

Would the stack trace where the object was allocated be sufficient?

[terrylucas]

We're adding both a stack trace when a particular class is constructed and a dominator view of objects belonging to the bound memory of other objects. I suspect both of these will help in whittling down the real culprit(s).

…

On Thu, Jan 7, 2021 at 2:11 PM Jacob Richman ***@***.***> wrote: Would the stack trace where the object was allocated be sufficient? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#1292 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAPV5QPZPXV5UPB6ULJX3STSYYWRTANCNFSM4JIUCQLQ> .

[venkatesh-sharechat]

That should work fine.

[kenzieschmoll]

This issue is superseded by new DevTools features. The memory screen now includes 'Diff' and 'Tracing' panes that provide dominate tree and allocation stack traces, addressing the need to find leaking classes. If there is more work to do here, please let us know by filing a new issue with up to date information. Thanks!