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

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

Predator and CL could not provide any possible suspects.

Using Code Search for the file, "api-arguments-inl.h" suspecting the below Cl might have caused this issue

Suspect CL: https://chromium.googlesource.com/v8/v8.git/+/bd93135e4ed21ce20268963cfd5db787b2646519%5E%21/src/api-arguments-inl.h

cbruni@ -- Could you please check whether this is caused with respect to your change, if not please help us in assigning it to the right owner.

Thanks!

My changes were too generic to cause this bug, I probably just changed the function singature of FunctionCallbackArguments.

From the msan output (or the lack thereof)  it looks like some internal msan issue (maybe this is n:
	[17655:17680:0519/105041.395907:ERROR:zygote_host_impl_linux.cc(270)] Failed to adjust OOM score of renderer with pid 17687: Permission denied (13)
MemorySanitizer:DEADLYSIGNAL
==1==ERROR: MemorySanitizer: ABRT on unknown address 0x053900000001 (pc 0x7f58f1e55428 bp 0x7ffcd9830be0 sp 0x7ffcd9830a98 T1)


If not, then the next best candidate is runner::WebAXObjectProxy::MisspellingsCount()

Temporarily assigning over to eugenis@ for the possible MSAN issue, if this is not the case ektar@ might be the next best guess to handle this issue.

The NextAction date has arrived: 2018-06-11

ClusterFuzz has detected this issue as fixed in range 567498:567499.

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

Fuzzer: ochang_domfuzzer
Job Type: linux_msan_content_shell_drt
Platform Id: linux

Crash Type: Abrt
Crash Address: 0x053900000001
Crash State:
  test_runner::WebAXObjectProxy::MisspellingsCount
  gin::internal::Dispatcher<int
  v8::internal::FunctionCallbackArguments::Call
  
Sanitizer: memory (MSAN)

Regressed: https://clusterfuzz.com/revisions?job=linux_msan_content_shell_drt&range=535692:535694
Fixed: https://clusterfuzz.com/revisions?job=linux_msan_content_shell_drt&range=567498:567499

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

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

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