Skip to content

The framework/CLI is missing tooling (or documented tooling) on how to debug raster cache issues #87836

@jonahwilliams

Description

@jonahwilliams

For example, SVGs benefit extensively from raster caching - yet I mostly discovered there were raster cache problems by setting breakpoints in the engine. If we have tooling to debug this for framework/google3 users, then we need to document it. If we don't then we should consider adding ways to pull raster cache information such as whether or not a picture was raster cached, when it was evicted, how frequently the cache is hit vs missed.

This also ties in with #87835, because without good tooling it is difficult/impossible to documented how to use it

Metadata

Metadata

Assignees

No one assigned

    Labels

    P2Important issues not at the top of the work lista: devtoolsDevTools related - suite of performance and debugging toolsc: performanceRelates to speed or footprint issues (see "perf:" labels)frameworkflutter/packages/flutter repository. See also f: labels.team-frameworkOwned by Framework teamtoolAffects the "flutter" command-line tool. See also t: labels.triaged-frameworkTriaged by Framework team

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions