Automatically applying components based on crash stacktrace and information from OWNERS files.

If this is incorrect, please apply the Test-Predator-Wrong-Components label.

Automatically assigning owner based on suspected regression changelist https://chromium.googlesource.com/v8/v8/+/e4402ed0bce568fbef7ee4bf8cd8ca47b62e4445 (Ensure ArrayBuffers are not neutered twice).

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.

Deepti - Clusterfuzz found a place where ArrayBuffers get neutered twice in Chrome! I'll investigate this today.

This issue is ultimately due to a spec inconsistency: https://github.com/tc39/ecma262/issues/1024

It's slated to be discussed at the TC39 meeting next week. Because this is a safe crash (CHECK, rather than some rogue memory access), I think we should wait and see what the outcome of TC39 is and then fix it according to the spec.

ClusterFuzz has detected this issue as fixed in range 543641:543642.

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

Fuzzer: inferno_layout_test_unmodified
Job Type: linux_asan_chrome_mp
Platform Id: linux

Crash Type: Ill
Crash Address: 0x558aeefb8448
Crash State:
  v8::internal::JSArrayBuffer::Neuter
  v8::ArrayBuffer::Neuter
  blink::DOMArrayBuffer::Transfer
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=linux_asan_chrome_mp&range=542736:542738
Fixed: https://clusterfuzz.com/revisions?job=linux_asan_chrome_mp&range=543641:543642

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

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 6610645202763776 is verified as fixed, so closing issue as verified.

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

The NextAction date has arrived: 2018-03-27