I don’t know what’s going to happen once I hit the memory heap limit, and am curious if anyone here has hit the heap limit or tested out what it’s like to tip-toe on the edge and see what happens right when one goes over (4GB). A few questions. What happens to the existing data in the canister? W…

Actually the memory_allocation docs are a bit misleading. As Roman replied to the other question about compute allocation, it accumulates over time like storage cost. Therefore, if you set a higher value for compute allocation, it’s expected that your canister will run out of cycles sooner than if …

We have issue with one of our asset canister here, its heap memory is full (more than 4.2Gb) and now it is un-responding. So I’m afraid that we have effectively lost all the assets that are on this canister, as even light queries don’t work. (Only status from dfx works) [image] So I guess you ha…

[image] dymayday: We have issue with one of our asset canister here, its heap memory is full (more than 4.2Gb) and now it is un-responding. So I’m afraid that we have effectively lost all the assets that are on this canister Thank you for your sacrifice and contributions to the community. Thi…

Rest in peace lil canister :pray: There is no upgrade involved here. The canister is a data bucket from a modified Rust bigmap-poc implementation. For our current needs, it is not supposed to be upgraded.

So was this Rust or Motoko code?

If you are talking to me, we only use Rust.

There is support for “splitting” a data canister in bigmap-poc. It’s not the most optimal split, but it exists. Seems like there is a bug in the code that calculates the canister size and thus the splitting never started? Or you don’t run the periodic maintenance checks within the bigmap-poc @dyma…

[image] icme: Curious though, it sounds like the unresponsive mess is due to overflowing the heap during an upgrade, and not during an update/query call (which would have just trapped). I’m not sure I understand how the heap would overflow during an upgrade and you wouldn’t get a trap. If you…

@sat The maintenance method is apparently not working on the amount of data we have in our canisters because of cycles limitations. Was the periodic maintenance supposed to be run periodically enough so it will manage to always complete despite cycle limitations ?

@dymayday well that’s unfortunate. Without the “maintenance” call running, this is bound to happen, since the amount of data in the canister will keep growing forever, until this limit is hit. I wasn’t aware that the cycle limit is being hit. Back when the code was developed (and that was a while a…

What happens when a canister hits the memory heap limit?

Developers

goose May 31, 2022, 1:17am 19

Rust stable memory manage; rust use 8GB stable memory

Topic		Replies	Views
PSA: Upcoming Wasm memory limit may break your canisters Developers	19	2427	August 28, 2024
Proposal: Help prevent canister heap overflow by adding heap_memory_size to canister_status Developers Discussing	5	367	March 31, 2024
Heap out of bounds ， use motoko Developers Functional-Programming	45	3331	June 22, 2023
Canister burning through cycles Developers	43	2024	August 4, 2022
Two questions about canister storage Developers	30	3555	March 9, 2022

What happens when a canister hits the memory heap limit?

Related topics