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

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

This issue looks similar to  bug 836942 , hence assigning to hongchan@ for more updates.

hongchan@ Could you please take a look in to this issue?

Thanks!

Same as the closed issue before: it is not locally reproducible. I can't understand how the repro case can happen.

ClusterFuzz has detected this issue as fixed in range 557110:557111.

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

Fuzzer: inferno_twister
Job Type: linux_msan_content_shell_drt
Platform Id: linux

Crash Type: Null-dereference READ
Crash Address: 0x000000000058
Crash State:
  blink::AudioNode::Handler
  blink::AudioDestinationNode::GetAudioDestinationHandler
  blink::BaseAudioContext::NotifyWorkletIsReady
  
Sanitizer: memory (MSAN)

Regressed: https://clusterfuzz.com/revisions?job=linux_msan_content_shell_drt&range=551933:551934
Fixed: https://clusterfuzz.com/revisions?job=linux_msan_content_shell_drt&range=557110:557111

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

Additional requirements: Requires HTTP

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 5925149103357952 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-05-14