Wasm memory growth limits without garbage collection

WebAssembly modules using linear memory face constraints when dynamically growing memory without garbage collection. The current Wasm specification (as of 2023) requires manual memory management, leaving developers to handle allocation and deallocation explicitly or via foreign function interfaces (FFIs).

Without the `wasm-gc` proposal finalized, applications risk memory leaks or hitting runtime limits if growth isn't carefully controlled. The `WebAssembly.Memory` object in JavaScript allows resizing, but uncontrolled growth can exhaust available memory or cause performance degradation.

How can developers safely implement dynamic memory growth in Wasm modules while avoiding leaks or hitting runtime limits? What strategies exist to monitor and constrain memory usage before the `wasm-gc` proposal is standardized? Are there tools or patterns to detect potential leaks during development?