Enable offline debugging of widget trees
Open
customer: money (g3)
offline
P2
screen: inspector
- Dominant language
- Dart
- Stars
- 1.7k
- Forks
- 404
- Avg merge
- 6d 17h
- Merged PRs (30d)
- 18
Description
This would allow apps to dump a snapshot of their widget tree and send it over when debugging memory and/or performance issues.
It would also allow us to build tooling to analyze highly complex scenes with 100s of widgets and generate a report.
Contributor guide
Research direction
No files, tests, or entry points are named. Start by mapping how DevTools currently represents widget trees and handles debugging data, then define the snapshot and transfer boundaries. Done should include offline widget-tree analysis and reporting for complex scenes, including memory or performance investigations.
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
- 25/100