Wasmtime GitHub notifications bot (Aug 27 2025 at 15:32): Wasmtime GitHub notifications bot (Aug 27 2025 at 15:32):dicej opened issue #11552:
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.
Wasmtime GitHub notifications bot (Aug 27 2025 at 15:32):dicej added the wasm-proposal:component-model-async label to Issue #11552.
Wasmtime GitHub notifications bot (Sep 15 2025 at 16:00):alexcrichton assigned dicej to issue #11552.
Wasmtime GitHub notifications bot (Feb 26 2026 at 21:39):alexcrichton commented on issue #11552:
https://github.com/bytecodealliance/wasmtime/pull/12652 added a built-in limit to all
ResourceTables which partly solves this, but the internal table used by async isn't reachable for embedders meaning the limit can't be configured. Thus I think this is still applicable.
Wasmtime GitHub notifications bot (Mar 11 2026 at 20:38):alexcrichton closed issue #11552:
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.
Last updated: Mar 23 2026 at 16:19 UTC