Skip to content

[web] Reduce CanvasKit's initial memory allocation #159499

New issue
New issue
Closed
flutter/engine
#56900
Closed
[web] Reduce CanvasKit's initial memory allocation#159499
flutter/engine
#56900
Assignees
mdebbar
Labels
P1High-priority issues at the top of the work liste: web_canvaskitCanvasKit (a.k.a. Skia-on-WebGL) rendering backend for Webengineflutter/engine related. See also e: labels.perf: memoryPerformance issues related to memoryplatform-webWeb applications specificallyteam-webOwned by Web platform teamtriaged-webTriaged by Web platform team
@mdebbar

Description

@mdebbar
mdebbar
opened on Nov 26, 2024

Currently, CanvasKit eagerly allocates 128MB of wasm memory. Let's try to reduce that to 64MB or 32MB.

The reason we can do it is because most image decoding is now done by the browser (PR).

Metadata

Metadata

Assignees

Labels

P1High-priority issues at the top of the work liste: web_canvaskitCanvasKit (a.k.a. Skia-on-WebGL) rendering backend for Webengineflutter/engine related. See also e: labels.perf: memoryPerformance issues related to memoryplatform-webWeb applications specificallyteam-webOwned by Web platform teamtriaged-webTriaged by Web platform team

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions