Wasmtime GitHub notifications bot (Aug 25 2020 at 23:38): Wasmtime GitHub notifications bot (Aug 25 2020 at 23:38):alexcrichton opened Issue #2163:
One of our fuzz bugs on OSS-Fuzz is that we're timing out when running the equivalent of
wasm-opt -ttf. This timeout means that we don't even start executing wasmtime to compile/instantiate the wasm module. We should investigate this and see if we can improve this to avoid hitting the timeout, for example:
- Not compiling binaryen with fuzzing flags
- Running
wasm-opt -ttfout-of-process to avoid fuzzing itself- Seeing if this is a bug in
wasm-opt -ttfwhere something is looping more than expected.For now we're likely to just ignore the fuzz failure, but the fuzzers would be more effective on oss-fuzz if we could fix this!
Wasmtime GitHub notifications bot (Oct 29 2020 at 15:03):alexcrichton closed Issue #2163:
One of our fuzz bugs on OSS-Fuzz is that we're timing out when running the equivalent of
wasm-opt -ttf. This timeout means that we don't even start executing wasmtime to compile/instantiate the wasm module. We should investigate this and see if we can improve this to avoid hitting the timeout, for example:
- Not compiling binaryen with fuzzing flags
- Running
wasm-opt -ttfout-of-process to avoid fuzzing itself- Seeing if this is a bug in
wasm-opt -ttfwhere something is looping more than expected.For now we're likely to just ignore the fuzz failure, but the fuzzers would be more effective on oss-fuzz if we could fix this!
Last updated: Dec 23 2024 at 12:05 UTC