Design - go/devtools-memory-eval-and-browse-design
Discuss UX deeper: go/notes-heap-browsing-use-case
Drop one object in snapshot to console
Browse references for one object in snapshot
- do we need to see refs always? nope, just for items from snapshot (discussed with Kenzie and Jacob)
- make limit for number of items configurable
- browse dead items
- live
  - inbound
    - getInboundReferences fails on json parsing dart-lang/sdk#51100
    - implement and test
  - outbound
    - list
    - map
    - class
    - record
    - closure
- static
  - select exact object for heap
  - outbound
  - inbound
Browse set of objects
- request: Make _getInstanceAsArray a public RPC dart-lang/sdk#51393
- all instances of class
- include implementers and subclasses
Enable for snapshot diff
Reroot browsing
Name variable and eval it
- Eval with running application
- Save variable with name
- Eval expression with saved variable
- Handle expiration of variables
Add more options to popup menu on snapshot
UX Review
- host: go/notes-eval-and-browse-ux-review
- follow up
  - Simple
  - Find root
  - Null reference exception
  - Set of objects - broken references
Integration testing
Share eval for inspector items with phoenix
Make sure GA is configured for browse menu
Bug bash
- run
- fix issues
release (remove flag) - Enable eval and browse. #5542
Documentation
- go/devtools-memory-documentation-updates-part-1
  - Draft
  - Tech review
  - Tech writing review
  - land PR
- http://go/devtools-memory-documentation-updates
  - Draft
  - Tech review
  - Tech writing review
  - land PR
Refactor code for maintainability

Memory: enable eval and browse #4962

Description

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions