Skip to content

Add an example demonstrating how to load your assets sequentially to reduce memory usage on web platforms #12653

Open

Description

What problem does this solve or what need does it fill?

On WASM, memory cannot be reclaimed / freed. As a result, loading all of your assets up front in a loading-screen pattern will balloon your memory usage and it will never go back down. See #12057 for more context.

What solution would you like?

Add an example demonstrating how to load assets one at a time, and then moving them onto the GPU using RenderAssetUsage once loaded.

Explain why this is useful for web.

What alternative(s) have you considered?

We could make this the default behavior on wasm.

Additional context

This came up when helping a commercial user debug performance issues on iOS.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Assignees

No one assigned

    Labels

    A-AssetsLoad files from disk to use for things like images, models, and soundsC-ExamplesAn addition or correction to our examplesC-PerformanceA change motivated by improving speed, memory usage or compile timesO-WebSpecific to web (WASM) builds

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions