Stream: wamr

Topic: Questions regarding memory allocation strategies

Antoine Lavandier (Jan 08 2026 at 13:30):

Hi,
I'm trying to use WAMR on top of some rust OS using the wamr-rust-sdk crate. This is only for testing/benchmarking pupose so I'm not worried about doing a proper port.
Anyway, after tinkering around I was able to compile to run on an NRF52840DK (Thumbv7 arch) and I have had errors regarding allocations. After tracking the source of my error, I realized that this is because I stubbed os_mmap from the platform_api_vmcore.h. I'm surprised by this being an issue for two reasons:

• This function is in a section called APIs required by WAMR AOT and compiled without AOT support and in the configuration specified that I wanted to run the interpreter.
• I used the memory pool allocation strategy instead of using the system alloc strategy.

This leads me to the following questions :

• Did I misunderstand something ?
• What does the memory pool strategy do if not use the provided pool to put the linear memory of the instances ?
• It seems to require more memory that I would have thought: loading the modules fails when the pool is under 120 KiB, despite the module weighing 262 bytes by itself and the linear memory seemingly not being part of the equation.

The exact allocation path is related to the linear memory of the instance i'm trying to build. I'm using WAMR 2.3.1, the version used by the wamr-rust-sdk

Thanks in advance

Last updated: Jan 09 2026 at 13:15 UTC