I’m not sure why 117 MB is being consumed, but I did find a reason for 89 MB of that memory usage. The canister writes and reads to stable memory in the pre/post_upgrade hook when the canister code is upgraded. Since the memory used for this purpose is never freed, it remains consumed.
My implementation doesn’t have anything unusual and follows the example of the stable structure crate.
@ielashi, similar to the answer you gave me the yesterday, I assume there’s no way to free the memory of a VirtualMemory<DefaultMemoryImpl>, right?
And btw., do you have an idea what is the reason for the 28 MB remaining consumed given that none of the other memory holds data?
// in WASM pages
{
db:1
assets:1
upgrade:1371
content_chunks:1
}