Skip to content

Add configurable limit for max number of resource/waitable/etc. handles #11552

@dicej

Description

@dicej

Each waitable (e.g. subtask, stream, or future), waitable-set, error-context, and host-implemented resource created by a guest uses host memory, and these could potentially add up and overwhelm the host unless limited. Similar to how we limit other resources like instances, tables, memory, etc., we should probably enforce a handle limit by default and make that configurable by the embedder.

Metadata

Metadata

Assignees

Labels

Type

No type

Projects

Status

Done

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions