Skip to content

Document the memory usage characteristics of using multiple FlutterEngines #37643

New issue
New issue
Closed
Closed
Document the memory usage characteristics of using multiple FlutterEngines#37643
Labels
P3Issues that are less important to the Flutter projecta: existing-appsIntegration with existing apps via the add-to-app flowc: performanceRelates to speed or footprint issues (see "perf:" labels)engineflutter/engine related. See also e: labels.
@xster

Description

@xster
xster
opened on Aug 5, 2019

Specifically when not all FlutterEngine instances are simultaneously visible. Could multiple FlutterEngines instances be a feasible and economic way of representing multiple UI and navigation states like webviews.

Metadata

Metadata

Assignees

No one assigned

    Labels

    P3Issues that are less important to the Flutter projecta: existing-appsIntegration with existing apps via the add-to-app flowc: performanceRelates to speed or footprint issues (see "perf:" labels)engineflutter/engine related. See also e: labels.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions