Re: [apache/incubator-teaclave] [WAMR] Fix leaked resources (PR #569)

[Qinkun Bao <no...@github.com.INVALID>]

> Good to see unloading the WASM's workload gracefully by adding corresponding native callbacks and preventing resource from leaking. However, there is a following issue identified by CI
> 
> ```
> thread '<unnamed>' panicked at 'assertion failed: self.buffer.is_empty() ||
>     self.opt.cmp.cmp(self.last_key.as_slice(), key) == Ordering::Less', common/rusty_leveldb_sgx/src/block_builder.rs:60:9
> stack backtrace:
> ```
> 
> It looks related to double release problem. probably need another patch to fix it ahead. thanks.

@bigdata-memory Thanks for the review. The CI issue has been patched in https://github.com/apache/incubator-teaclave/pull/570.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/apache/incubator-teaclave/pull/569#issuecomment-956764579