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.

Sign up for GitHub

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

Jump to bottom

[Proposal]Profiling memory usage per isolate #8685

Open
srmncnk opened this issue Jan 9, 2025 · 1 comment
Open

[Proposal]Profiling memory usage per isolate #8685

srmncnk opened this issue Jan 9, 2025 · 1 comment
Labels
cost: medium Medium engineering cost to implement new feature P2 important to work on, but not at the top of the work list. screen: memory Issues with the Memory screen.

Comments

@srmncnk
Copy link

srmncnk commented Jan 9, 2025

Use case

I would like to profile memory usage of my app per isolate. Currently in profiler I can't find a way to separate allocations per each isolate. I tried to do it programatically by connecting to the websocket of the profiling session, but even after a few attempts to get allocations per isolate, I don't really trust the results. I'm using flutter_isolate and background_locator plugins which basically create their own FlutterEngine.

Proposal

I'd like to have a combo box in the profiles which separates allocations for each isolate.
@maheshj01
Copy link
Member

Seems like a valid proposal to me

@maheshj01 maheshj01 changed the title Profiling memory usage per isolate [Proposal]Profiling memory usage per isolate Jan 10, 2025
@kenzieschmoll kenzieschmoll transferred this issue from flutter/flutter Jan 10, 2025
@kenzieschmoll kenzieschmoll added screen: memory Issues with the Memory screen. new feature cost: medium Medium engineering cost to implement P2 important to work on, but not at the top of the work list. labels Jan 10, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
cost: medium Medium engineering cost to implement new feature P2 important to work on, but not at the top of the work list. screen: memory Issues with the Memory screen.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@srmncnk @maheshj01 @kenzieschmoll