alexcrichton opened PR #10026 from alexcrichton:fuzz-move-less-data
to bytecodealliance:main
:
Previously a limit was added which prevented more than N growths over time but this wasn't sufficient to prevent a test case from continuously growing memory by just enough that it never went over N but the byte sizes in question were big enough that the fuzz test case timed out on OSS-Fuzz.
This commit changes the check to limit "bytes moved" instead of the quantity of growths over time. This is a coarse approximation of what's happening but should hopefully still allow interesting behavior while additionally ensuring we don't spent the whole time moving around gigabytes of data.
<!--
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.htmlPlease ensure all communication follows the code of conduct:
https://github.com/bytecodealliance/wasmtime/blob/main/CODE_OF_CONDUCT.md
-->
alexcrichton requested fitzgen for a review on PR #10026.
alexcrichton requested wasmtime-fuzz-reviewers for a review on PR #10026.
github-actions[bot] commented on PR #10026:
Subscribe to Label Action
cc @fitzgen
<details>
This issue or pull request has been labeled: "fuzz-bug", "fuzzing"Thus the following users have been cc'd because of the following labels:
- fitzgen: fuzzing
To subscribe or unsubscribe from this label, edit the <code>.github/subscribe-to-label.json</code> configuration file.
Learn more.
</details>
fitzgen submitted PR review.
fitzgen merged PR #10026.
Last updated: Jan 24 2025 at 00:11 UTC