CHECK failure: !!(flags & HitTestRegionFlags::kHitTestAsk) == !!async_hit_test_reasons in aggre |
|||
Issue descriptionDetailed report: https://clusterfuzz.com/testcase?key=5176784485875712 Fuzzer: libFuzzer_hit_test_manager_fuzzer Job Type: libfuzzer_chrome_asan_debug Platform Id: linux Crash Type: CHECK failure Crash Address: Crash State: !!(flags & HitTestRegionFlags::kHitTestAsk) == !!async_hit_test_reasons in aggre viz::AggregatedHitTestRegion::AggregatedHitTestRegion viz::HitTestAggregator::SetRegionAt Sanitizer: address (ASAN) Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=607980:607986 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=5176784485875712 Issue filed automatically. See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reference.md for more information.
,
Dec 1
Automatically adding ccs based on OWNERS file / target commit history. If this is incorrect, please add ClusterFuzz-Wrong label.
,
Dec 1
Automatically assigning owner based on suspected regression changelist https://chromium.googlesource.com/chromium/src/+/567005d56ccb3072bd723c3422997d0c42546b69 (Add viz hit test surface layer metrics). 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. |
|||
►
Sign in to add a comment |
|||
Comment 1 by ClusterFuzz
, Dec 1Labels: Test-Predator-Auto-Components