[foozzie] Suppress OOM output when using correctness fuzzer

Otherwise we report a spurious difference after OOM.

Bug: chromium:1052849
Change-Id: I795f7393a8061ff41178295d49bdaea411d3c461
Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2060307
Reviewed-by: Ulan Degenbaev <ulan@chromium.org>
Commit-Queue: Michael Achenbach <machenbach@chromium.org>
Cr-Commit-Position: refs/heads/master@{#66292}
This commit is contained in:
Michael Achenbach 2020-02-17 15:27:15 +01:00 committed by Commit Bot
parent 0c25872503
commit 56e5d6a266

View File

@ -453,11 +453,13 @@ void i::V8::FatalProcessOutOfMemory(i::Isolate* isolate, const char* location,
// BUG(1718): Don't use the take_snapshot since we don't support
// HeapObjectIterator here without doing a special GC.
isolate->heap()->RecordStats(&heap_stats, false);
char* first_newline = strchr(last_few_messages, '\n');
if (first_newline == nullptr || first_newline[1] == '\0')
first_newline = last_few_messages;
PrintF("\n<--- Last few GCs --->\n%s\n", first_newline);
PrintF("\n<--- JS stacktrace --->\n%s\n", js_stacktrace);
if (!FLAG_correctness_fuzzer_suppressions) {
char* first_newline = strchr(last_few_messages, '\n');
if (first_newline == nullptr || first_newline[1] == '\0')
first_newline = last_few_messages;
PrintF("\n<--- Last few GCs --->\n%s\n", first_newline);
PrintF("\n<--- JS stacktrace --->\n%s\n", js_stacktrace);
}
}
Utils::ReportOOMFailure(isolate, location, is_heap_oom);
// If the fatal error handler returns, we stop execution.