Browse Source
* Release Wasmtime 5.0.0 [automatically-tag-and-release-this-commit] * Update release notes for 5.0.0 (#5539) * Fix a debug assert with `wasm_backtrace(false)` (#5580) This commit fixes an issue where when backtraces were disabled but a host function returned an error it would trigger a debug assertion within Wasmtime. The fix here is to update the condition of the debug assertion and add a test doing this behavior to ensure it works in the future. I've also further taken the liberty in this commit to remove the deprecation notice for `Config::wasm_backtrace`. We don't really have a strong reason for removing this functionality at this time and users have multiple times now reported issues with performance that seem worthwhile to keep the option. The latest issue, #5577, has a use case where it appears the quadratic behavior is back in a way that Wasmtime won't be able to detect. Namely with lots of wasm interleaved with host on the stack if the original error isn't threaded through the entire time then each host error will trigger a new backtrace since it doesn't see a prior backtrace in the error being returned. While this could otherwise be fixed with only capturing one contiguous backtrace perhaps this seems reasonable enough to leave the `wasm_backtrace` config option for now. Closes #5577 * Add component model wasmtime feature to Docs.rs (#5558) Co-authored-by: Wasmtime Publish <wasmtime-publish@users.noreply.github.com> Co-authored-by: Alex Crichton <alex@alexcrichton.com> Co-authored-by: Kyle Brown <kylebrw@gmail.com>pull/5937/head v5.0.0
wasmtime-publish
2 years ago
committed by
GitHub
5 changed files with 69 additions and 4 deletions
Loading…
Reference in new issue