AuroraMiddleware/v8
1
0
Fork 0
Code Issues 2 Pull Requests Releases Wiki Activity

[wasm][fuzzer] Run micro tasks after each fuzzer execution

Browse Source 
This asserts that we run e.g. GC finalization tasks. Without that, we
might run ouf of memory.

R=ahaas@chromium.org

Bug: chromium:938739
Change-Id: Ic80074f877183bcabb3353fbeff94842a534efab
Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1526007
Reviewed-by: Andreas Haas <ahaas@chromium.org>
Commit-Queue: Clemens Hammacher <clemensh@chromium.org>
Cr-Commit-Position: refs/heads/master@{#60266}
This commit is contained in:
Clemens Hammacher 2019-03-15 14:32:37 +01:00 committed by Commit Bot
parent c83aff3bf5
commit 2270c0eaaa
1 changed files with 4 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
test/fuzzer/wasm.cc
View File

@ -55,5 +55,9 @@ extern "C" int LLVMFuzzerTestOneInput(const uint8_t* data, size_t size) {
if (compiles) { if (compiles) {
i::wasm::fuzzer::InterpretAndExecuteModule(i_isolate, module_object); i::wasm::fuzzer::InterpretAndExecuteModule(i_isolate, module_object);
} }
// Pump the message loop and run micro tasks, e.g. GC finalization tasks.
support->PumpMessageLoop(v8::platform::MessageLoopBehavior::kDoNotWait);
isolate->RunMicrotasks();
return 0; return 0;
} }