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 adding ccs based on OWNERS file / target commit history.

If this is incorrect, please add ClusterFuzz-Wrong label.

Automatically assigning owner based on suspected regression changelist https://chromium.googlesource.com/chromium/src/+/ae872ca32aacde2d3449ceb40c1160dd7b304bd4 (Do not commit navigation to an arbitrary request in TestRenderFrame).

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 is fuzzing test code, which should not use '*' for subframe url. Our test harness does not support this scenario - so we have a CHECK there.

This crash occurs very frequently on windows platform and is likely preventing the fuzzer renderer_tree_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/+/c65b6a5b145f37feddca661905490d33ee1dbd4d

commit c65b6a5b145f37feddca661905490d33ee1dbd4d
Author: Dmitry Gozman <dgozman@chromium.org>
Date: Mon Jan 14 22:21:32 2019

Fix CHECK failure in fuzzer

Clusterfuzz claims to be blocked by this false alaram, so
we allow it proceed by replacing CHECK with some dummy values.

Bug:  919822 
Change-Id: I4ea696809cb5cddd3e1a168e1ad0ffa00e06127d
Reviewed-on: https://chromium-review.googlesource.com/c/1409454
Reviewed-by: Daniel Cheng <dcheng@chromium.org>
Commit-Queue: Dmitry Gozman <dgozman@chromium.org>
Cr-Commit-Position: refs/heads/master@{#622631}
[modify] https://crrev.com/c65b6a5b145f37feddca661905490d33ee1dbd4d/content/test/test_render_frame.cc

ClusterFuzz has detected this issue as fixed in range 622583:622637.

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

Fuzzer: libFuzzer_renderer_tree_fuzzer
Fuzz target binary: renderer_tree_fuzzer
Job Type: windows_libfuzzer_chrome_asan
Platform Id: windows

Crash Type: CHECK failure
Crash Address: 
Crash State:
  success in test_render_frame.cc
  content::TestRenderFrame::BeginNavigation
  blink::LocalFrameClientImpl::BeginNavigation
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=windows_libfuzzer_chrome_asan&range=620617:620632
Fixed: https://clusterfuzz.com/revisions?job=windows_libfuzzer_chrome_asan&range=622583:622637

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

See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reproducing.md for instructions to reproduce this bug locally.

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

ClusterFuzz testcase 6332534568517632 is verified as fixed, so closing issue as verified.

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