You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the stable version of Azle we have addressed a major memory leak with cross canister calls by cleaning up the global resolve and reject callbacks in a destructor in the on cleanup from ICP after every cross-canister call. We should apply these fixes to the experimental version of Azle as well.
Here's an example of an error found during fuzz testing that I believe was caused in part by this:
- [ ] fixed
canister: async_await functional
This is a similar error to the first one above...I wonder if they are the same error? This one looks easier to debug, so I say fix this one first.
```bash
requestId: ArrayBuffer {
[Uint8Contents]: <fc 7d 64 75 2f b9 db 6a dc 50 cb a4 a4 ee 84 70 80 cf e9 e0 24 38 64 15 6c 46 a4 7a 56 84 80 d5>,
byteLength: 32
},
response: {
ok: true,
status: 200,
statusText: 'OK',
body: { status: 'replied', certificate: [Uint8Array] },
headers: [ [Array], [Array], [Array], [Array] ]
},
reject_code: 5,
reject_message: 'Error from Canister bkyz2-fmaaa-aaaaa-qaaaq-cai: Canister called `ic0.trap` with message: Panic occurred: already borrowed: BorrowMutError at src/build/experimental/commands/compile/wasm_binary/rust/experimental_canister_template/src/ic/call_raw.rs:46.\n' +
'Consider gracefully handling failures from this canister or altering the canister to handle exceptions. See documentation: http://internetcomputer.org/docs/current/references/execution-errors#trapped-explicitly',
error_code: 'IC0503'
}
The text was updated successfully, but these errors were encountered:
In the stable version of Azle we have addressed a major memory leak with cross canister calls by cleaning up the global resolve and reject callbacks in a destructor in the on cleanup from ICP after every cross-canister call. We should apply these fixes to the experimental version of Azle as well.
Here's an example of an error found during fuzz testing that I believe was caused in part by this:
The text was updated successfully, but these errors were encountered: