Automatically assigning owner based on suspected regression changelist https://chromium.googlesource.com/v8/v8/+/7c79a9fd1e35d5272b5dbe57af92c7e0d2120ca3 ([bigint] Stage BigInts).

If this is incorrect, please let us know why and apply the Test-Predator-Wrong-CLs label. If you aren't the correct owner for this issue, please unassign yourself as soon as possible so it can be re-triaged.

The following revision refers to this bug:
  https://chromium.googlesource.com/v8/v8.git/+/2ce122e3f29e2ab27ce7bbca382ef9feab92cf06

commit 2ce122e3f29e2ab27ce7bbca382ef9feab92cf06
Author: Jakob Kummerow <jkummerow@chromium.org>
Date: Mon Mar 05 22:26:25 2018

[bigint] Fix GC unsafety issue

There must not be both an allocating function call and a handle deref
in the list of arguments to a call. Depending on the evaluation order
that the C++ compiler chooses, the deref could happen before the call
and the resulting raw pointer be invalidated by the GC.

Bug:  chromium:818424 
Change-Id: I525947252ff9d0b048a5bf82c2976e0acce739be
Reviewed-on: https://chromium-review.googlesource.com/949782
Reviewed-by: Adam Klein <adamk@chromium.org>
Commit-Queue: Jakob Kummerow <jkummerow@chromium.org>
Cr-Commit-Position: refs/heads/master@{#51746}
[modify] https://crrev.com/2ce122e3f29e2ab27ce7bbca382ef9feab92cf06/src/objects/bigint.cc

Fixed by #2.

This issue should have been caught by GCMole, but there was an oversight in that tool. vegorov@ has found the omission and will submit a fix. Thanks!

ClusterFuzz has detected this issue as fixed in range 51745:51746.

Detailed report: https://clusterfuzz.com/testcase?key=5145424592371712

Fuzzer: mbarbella_js_mutation
Job Type: windows_asan_d8
Platform Id: windows

Crash Type: Sanitizer CHECK failure
Crash Address: 
Crash State:
  "((res.trace)) != (0)" (0x0, 0x0)
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=windows_asan_d8&range=51672:51673
Fixed: https://clusterfuzz.com/revisions?job=windows_asan_d8&range=51745:51746

Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=5145424592371712

See https://github.com/google/clusterfuzz-tools for more information.

If you suspect that the result above is incorrect, try re-doing that job on the test case report page.

ClusterFuzz testcase 5145424592371712 is verified as fixed, so closing issue as verified.

If this is incorrect, please add ClusterFuzz-Wrong label and re-open the issue.