> First, hosts have no visibility on how memory is being managed within a guest. Want to diagnose memory leaks? Good luck with that. Is that really true? I thi

> First, hosts have no visibility on how memory is being managed within a guest. Want to diagnose memory leaks? Good luck with that. Is that really true? I think we can implement a memory allocator done by hosts. By using "import" feature of WASM, a guest could implement a memory allocator that imports functions from the host that ask the host to look through the gest's memory directly (it is possible in JS code) and then allocate one. Maybe it will be slower but it is certainly possible that hosts can know what is happening to the memory in this way.