Automatically assigning owner based on suspected regression changelist https://chromium.googlesource.com/chromium/src/+/808d1dbc8faa17e394f74376a8fdbdecd9d0696f (Do not check for memory leaks from CSP fuzzer initialization.).

If this is incorrect, please remove the owner and apply the Test-Predator-Wrong-CLs label.

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

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

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/6a02154b51b6cfcc7ec49a1a7b55bea4724e9e49

commit 6a02154b51b6cfcc7ec49a1a7b55bea4724e9e49
Author: Jeremy Roman <jbroman@chromium.org>
Date: Tue Oct 10 22:16:55 2017

CSP Fuzzer: Initialize the lsan disabled scope after Oilpan.

Bug:  770463 , 771855 
Change-Id: I681bd5c48cae4ddb2816961d85e2019e959e8763
Reviewed-on: https://chromium-review.googlesource.com/710512
Reviewed-by: Max Moroz <mmoroz@chromium.org>
Commit-Queue: Jeremy Roman <jbroman@chromium.org>
Cr-Commit-Position: refs/heads/master@{#507793}
[modify] https://crrev.com/6a02154b51b6cfcc7ec49a1a7b55bea4724e9e49/third_party/WebKit/Source/core/frame/csp/ContentSecurityPolicyFuzzer.cpp

ClusterFuzz has detected this issue as fixed in range 507766:507811.

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

Fuzzer: libFuzzer_content_security_policy_fuzzer
Job Type: libfuzzer_chrome_asan
Platform Id: linux

Crash Type: Null-dereference READ
Crash Address: 0x000000000000
Crash State:
  blink::ThreadState::Current
  blink::LeakSanitizerDisableScope::LeakSanitizerDisableScope
  blink::LLVMFuzzerInitialize
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan&range=506448:506530
Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan&range=507766:507811

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

See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reproducing.md 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 4638214731333632 is verified as fixed, so closing issue as verified.

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