Add functionality to track metrics about what is being repainted in a frame
- Dominant language
- Dart
- Stars
- 1.7k
- Forks
- 404
- Avg merge
- 6d 17h
- Merged PRs (30d)
- 18
Description
This stems from flutter.dev/go/drm-embedder
Question: "Would it be worth exploring a debugger mode that stores metrics about the average area being repainted or prints a history of the area repainted per frame?"
comment from @jacob314: "This would make sense to integrate with Flutter DevTools. Probably both aggregate metrics and metrics for each frame."What was the dirty rect for this frame that was slow?" Why are the dirty rects so large when very little is changing?"
Contributor guide
Research direction
Start by reviewing flutter.dev/go/drm-embedder and the existing DevTools frame-debugging surfaces; the issue names no files or tests. Establish how aggregate and per-frame repaint-area metrics could answer which dirty rect made a frame slow, then define the scope and completion criteria with the DevTools maintainers.
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