Automatically assigning owner based on suspected regression changelist https://chromium.googlesource.com/chromium/src/+/238613f2364a704efa82a4e252f6c2058d7b1924 (Fix build on case-sensitive file systems after the Great Blink mv.).

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.

This should be resolved by https://chromium.googlesource.com/chromium/src/+/52611a54cc13c259a6fa79b296a3038d84c0d442

This crash occurs very frequently on linux platform and is likely preventing the fuzzer renderer_fuzzer from making much progress. Fixing this will allow more bugs to be found.

Marking this bug as a blocker for next Beta release.

If this is incorrect, please add ClusterFuzz-Wrong label and remove the ReleaseBlock-Beta label.

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

commit cd81d2e64ffd7f6cace01432abe8b59b978914cd
Author: Kent Tamura <tkent@chromium.org>
Date: Tue Apr 10 04:19:13 2018

Update security_blacklist.txt and vptr_blacklist.txt for the Great Blink mv.

LifecycleObserver.h was renamed to lifecycle_observer.h.

TBR=thakis@chromium.org

Bug:  768828 ,  830210 
Change-Id: I26008bacc5ebb8446ec0a95e03ad1bd2f34cb102
Reviewed-on: https://chromium-review.googlesource.com/1004076
Reviewed-by: Kent Tamura <tkent@chromium.org>
Commit-Queue: Kent Tamura <tkent@chromium.org>
Cr-Commit-Position: refs/heads/master@{#549414}
[modify] https://crrev.com/cd81d2e64ffd7f6cace01432abe8b59b978914cd/tools/ubsan/security_blacklist.txt
[modify] https://crrev.com/cd81d2e64ffd7f6cace01432abe8b59b978914cd/tools/ubsan/vptr_blacklist.txt

ClusterFuzz has detected this issue as fixed in range 549412:549415.

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

Fuzzer: libFuzzer_renderer_fuzzer
Job Type: libfuzzer_chrome_ubsan
Platform Id: linux

Crash Type: Bad-cast
Crash Address: 0x348297904408
Crash State:
  Bad-cast to blink::ContextLifecycleObserver from blink::LifecycleObserver<blink::ExecutionContext, blink::ContextLifecycleObserver>
  blink::LifecycleObserver<blink::ExecutionContext, blink::ContextLifecycleObserver>::SetContext
  blink::ContextLifecycleObserver::ContextLifecycleObserver
  
Sanitizer: undefined (UBSAN)

Recommended Security Severity: High

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_ubsan&range=549059:549062
Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_ubsan&range=549412:549415

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

See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reference.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 has detected this issue as fixed in range 549412:549415.

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

Fuzzer: libFuzzer_renderer_fuzzer
Job Type: libfuzzer_chrome_ubsan
Platform Id: linux

Crash Type: Bad-cast
Crash Address: 0x348297904408
Crash State:
  Bad-cast to blink::ContextLifecycleObserver from blink::LifecycleObserver<blink::ExecutionContext, blink::ContextLifecycleObserver>
  blink::LifecycleObserver<blink::ExecutionContext, blink::ContextLifecycleObserver>::SetContext
  blink::ContextLifecycleObserver::ContextLifecycleObserver
  
Sanitizer: undefined (UBSAN)

Recommended Security Severity: High

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_ubsan&range=549059:549062
Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_ubsan&range=549412:549415

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

See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reference.md for more information.

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

This bug has been closed for more than 14 weeks. Removing security view restrictions.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot