WebAssembly / WebAssembly/binaryen
Fuzzer iteration takes over an hour
Open
Nobody has claimed this yet.
- Dominant language
- WebAssembly
- Stars
- 8.6k
- Forks
- 885
- Avg merge
- 1d 19h
- Merged PRs (30d)
- 69
Description
At commit 0d3c2eeb634913643f2cade4b5d738962b2308c2 I'm getting this:
$ time ./scripts/fuzz_opt.py --auto-initial-contents 2795924036512128284
<...>
real 87m56.269s
user 87m55.172s
sys 0m1.603s
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the report at commit 0d3c2eeb634913643f2cade4b5d738962b2308c2 using scripts/fuzz_opt.py and the supplied --auto-initial-contents value. Start by profiling or tracing this command to identify why one fuzzer iteration takes over an hour; done means the cause is understood and the iteration completes substantially faster.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python, wasm
- Domain
- compilers
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100