Stream: git-wasmtime

Topic: wasmtime / PR #10416 Report GC allocation requests that w...

Wasmtime GitHub notifications bot (Mar 17 2025 at 22:18):

fitzgen opened PR #10416 from fitzgen:instantiation-fuzzer-alloc-too-large to bytecodealliance:main:

Report these as Trap::AllocationTooLarge, rather than as generic anyhow::Errors, because they happen due to integer overflow when calculating allocation sizes or because the requested size is larger than the configured heap.

These failures are also expected during attempted instantiations, and our instantiation fuzzing oracle already correctly handles and ignores all traps (rather than panicking and failing the fuzz iteration) so this additionally has the affect of unblocking the fuzzers.

<!--
Please make sure you include the following information:

• If this work has been discussed elsewhere, please include a link to that
  conversation. If it was discussed in an issue, just mention "issue #...".

• Explain why this change is needed. If the details are in an issue already,
  this can be brief.

Our development process is documented in the Wasmtime book:
https://docs.wasmtime.dev/contributing-development-process.html

Please ensure all communication follows the code of conduct:
https://github.com/bytecodealliance/wasmtime/blob/main/CODE_OF_CONDUCT.md
-->

Wasmtime GitHub notifications bot (Mar 17 2025 at 22:18):

fitzgen requested alexcrichton for a review on PR #10416.

Wasmtime GitHub notifications bot (Mar 17 2025 at 22:18):

fitzgen requested wasmtime-fuzz-reviewers for a review on PR #10416.

Wasmtime GitHub notifications bot (Mar 17 2025 at 22:18):

fitzgen requested wasmtime-core-reviewers for a review on PR #10416.

Wasmtime GitHub notifications bot (Mar 17 2025 at 22:25):

alexcrichton submitted PR review.

Wasmtime GitHub notifications bot (Mar 17 2025 at 22:57):

fitzgen merged PR #10416.

Last updated: Apr 18 2025 at 09:03 UTC