[User reported] Memory screen feature parity with Xcode instruments
Open
cost: high
new feature
P2
screen: memory
- Dominant language
- Dart
- Stars
- 1.7k
- Forks
- 404
- Avg merge
- 6d 17h
- Merged PRs (30d)
- 18
Description
This is a user-reported issue from the 2025 DevTools user survey.
A user is requesting feature parity with Xcode instruments which the user reported helped them find a memory leak after they were unable to in DevTools.
Contributor guide
Research direction
The issue names no files, tests, or entry points. Start by locating the DevTools memory screen and reviewing how Xcode Instruments supports memory-leak investigation; clarify which capabilities are requested and define feature-parity acceptance criteria before implementation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- dart
- Domain
- devtools, performance
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100