8000 Document the memory usage characteristics of using multiple FlutterEngines · Issue #37643 · flutter/flutter · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Document the memory usage characteristics of using multiple FlutterEngines #37643

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign u 8000 p for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Closed
xster opened this issue Aug 5, 2019 · 1 comment
Closed

Document the memory usage characteristics of using multiple FlutterEngines #37643

xster opened this issue Aug 5, 2019 · 1 comment
Labels
a: existing-apps Integration with existing apps via the add-to-app flow c: performance Relates to speed or footprint issues (see "perf:" labels) engine flutter/engine repository. See also e: labels. P3 Issues that are less important to the Flutter project

Comments

@xster
Copy link
Member
xster commented 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.
@xster xster added engine flutter/engine repository. See also e: labels. c: performance Relates to speed or footprint issues (see "perf:" labels) a: existing-apps Integration with existing apps via the add-to-app flow labels Aug 5, 2019
@xster xster mentioned this issue Aug 5, 2019
Closed
@xster xster closed this as completed May 21, 2022
@github-actions
Copy link
github-actions bot commented Jun 4, 2022

This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of flutter doctor -v and a minimal reproduction of the issue.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jun 4, 2022
@flutter-triage-bot flutter-triage-bot bot added P3 Issues that are less important to the Flutter project and removed P6 labels Jun 28, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
a: existing-apps Integration with existing apps via the add-to-app flow c: performance Relates to speed or footprint issues (see "perf:" labels) engine flutter/engine repository. See also e: labels. P3 Issues that are less important to the Flutter project
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@chinmaygarde @xster @darshankawar
0